So: I'm using Ubuntu 12.04 64 bit; I've set up unixODBC, and I'm trying to open an ODBC connection in Julia. I've tried this on both stable 0.20 and the latest nightly of Julia 0.30; I'm using ODBC.jl version 0.3.1. The problem I hit is that Julia seems to not be loading my DSNs. For instance:
ulia> ODBC.listdsns()
0x2 Array{String,2}
On the other hand, isql can connect to my DSNs just fine (so unixODBC is set up correctly). So... now I'm not sure how to proceed. I've tried using ODBC.advancedconnect(), but oddly, I get the same error message as when I try to use a DSN:
IM002: [unixODBC][Driver Manager]Data source name not found, and no default driver specified
There is a note about setting const odbc_dm on the ODBC.jl github page; I can't find any libs that sound like the one that note is talking about, but maybe that's the problem?
Any suggestions appreciated -- I don't particularly know how to proceed with this one, so this posting feels a little spare on details. If there's more information that would be helpful, just let me know and I'll get it posted.
ODBC.jl developer here. Yeah, it's probably because the package isn't finding your unixODBC library. Once you run using ODBC, type ODBC.odbc_dm to see what the package is picking up. You may have to manually set it (by modifying the ODBC_types.jl file in your package directory, or I can add some better logic to pick it up (better long-term). Feel free to open an issue at the repo and we can troubleshoot from there.
Related
I've searched for tutorials to help configure the package in my PC, and I've found this one: https://www.youtube.com/watch?v=_fDhRL_LBdQ
I executed every part of the code interactively with the tutorial, but when I run ee_install() (after installing miniconda with py_discover_config() and other packages previously, such as reticulate), but it keeps me returning an error saying that anaconda is mandatory for the package since I'm a windows user.
Here is the error I get:
Error in ee_install_set_pyenv_env(py_env = py_env, py_path = python_path, : Windows users must install miniconda/anaconda to use rgee. The use of a Python environment is mandatory.
I've just installed Anaconda (full version with navigator) and I set a new python environment called "py2r" and tried to use the function ee_install_set_pyenv(), passing the path to the environment created through Anaconda Navigator (which has a python.exe) as paremeter to py_path and the name "py2r" as paremeter for py_env arg. And yet, it didn't work.
What am I missing?
In case you want to take a look at the code, I can provide it, but I don't think it's necessary because is a simple test script that follows as I described.
Thanks for your attention and congratulations for the library, it will be very usefull for me at work!
I fixed the ee_install() problems bypassing them and doing every passage manually. It will require no more then 10 mins and you will probably fix the installation problems. You can find and follow the manual installation with this tutorial:
https://www.youtube.com/watch?v=1-k6wNL2hlo
I installed Scilab 5.5.2 on Windows 10, and then installed the Scilab Code Generator toolbox.
However, when I start Scilab, the following message appears and I can't use the toolbox. This problem occurs for every toolbox.
Start Scilab Code Generator
Version: 0.9.20190122
Load macros
atomsLoad: An error occurred while loading 'xcos_code_generator-0.9.20190122':
File "C:\Users\光\AppData\Roaming\Scilab\SCILAB~1.2\atoms\x64\XCOS_C~1\09E129~1.201\macros\names" does not exist or read access denied.
(光 is my username.)
I suppose the problem comes from "\Scilab\SCILAB~1.2" in the middle of the file path. In my computer, the only folder in "Scilab" is "scilab-5.5.2", so indeed the software cannot find the file it's looking for.
Does anyone have any ideas?
I need to use the toolbox at work soon, so any help is greatly appreciated. Thank you in advance.
Note: I'm not using the latest Scilab 6.0.2 because it fails to work on my computer. It closes immediately after I open it.
I solved the problem by myself.
It was my user name "光" that caused the problem. I found people saying that user names in full-width characters such as Japanese sometimes cause problems like this.
The solution is to create another user account with a name in half-width characters and install Scilab in that account. (Just changing the full-width user name doesn't work because it doesn't change the filenames that already exist.)
I couldn't find the solution until today because I was searching for solutions only in the context of Scilab, not in the context of software in general.
I hope this answer helps someone.
I'm not sure why you are using an outdated version of Scilab. The latest version is 6.0.2 on Windows. If the newer version doesn't work properly then that's the problem you need to fix first. To test your Scilab installation you may run it in the terminal. Find the installation folder. For me, it is C:\Program Files\scilab-6.0.2\bin the on cmd go to the path and run Scilex.exe. If not uninstall everything and install it in a proper way. My recommendation is to uninstall the old Scilab you already have. Then:
Install Chocolatey package manager
Open PowerShell as Admin and run choco update all -y, once in a while update your packages this way.
run choco install Scilab -y
then open the Scilab software
run the atomsInstall("xcos_code_generator") in the console
runt the atomsLoad("xcos_code_generator") to make sure your package is installed properly. You should see this as a result:
--> atomsInstall("xcos_code_generator")
Scanning repository http://atoms.scilab.org/6.0 ... Done
ans =
!xcos_code_generator 0.9.201901 user SCIHOME\atoms\x64\xcos_code_generator\0.9.201901 I !
--> atomsLoad("xcos_code_generator");
Start Scilab Code Generator
Version: 0.9.20190122
Load macros
Load help
Load demos
I have installed meld 3.14.2, at last (on NFS share in Redhat 6.3 server), after nearly 40 hours of efforts , installing each and every dependency and at last seems to be successful. But one finale error needs to be solved:
(meld:20703): GLib-GIO-ERROR **: No GSettings schemas are installed on the system
Trace/breakpoint trap (core dumped)
There was answer here: GLib-GIO-ERROR**: No GSettings schemas are installed on the system
I am not aware of these jargons before. So, please explain in detail what to do.
Do I need to set the variable $XDG_DATA_DIR or not? And if, why and what should be the value?
And I can find that the compiled file is already located in MyApp/share/glib-2.0/schemas.
However, I have also tried the following, even though the compiled schema is already there:
glib-complile-schemas <PATH_TO_SCHEMAS> --targetdir=MyApp/share/glib-2.0/schemas
But still I am getting the error. I have tried the variable too by setting it to MyApp and MyApp/share/glib-2.0/schemas. That too doesn't work.
I have also tried reinstalling gsettings-desktop-config. Still error. In my case, it's 3.12 version.
So, what's going on here?? Please explain. I have been sleepless. :(
Thanks you!
And also for your information, I have installed all the dependencies GTK+,ATK,CAIRO,PANGO etc... under the same installation directory with prefix=<base>/meld/deps.
Example:
meld binaries resides as follows: <base>/meld/bin/
cairo binaries are installed as follows: <base>/meld/deps/bin/
atk binaries are installed as follows: <base>/meld/deps/bin/
Similarly, you can think of other dependencies
Well I am unsure why you are installing it to its own prefix... but just setting GSETTINGS_SCHEMA_DIR to the full path to the schema dir should work.
I downloaded Vim 7.3 and installed it on my Windows7 64 bit system. I coded a simple python 3.4 program and tried to run it without success using the :!python COMMAND. When I checked version, bottom of output said:
Dependency: python27.dll, python33.dll, x64-msvcrt-ruby200.dll, lva52.dll, libintl.dll, lidiconv.dll, iconv.dll.
When I checked, python27.dll is not found on my system at all, python33.dll is in a directory for a program called "Autodesk 123D Design". I didn't check for the others yet. Can someone explain if these are required and if so, where they go? I have no idea why they would not have downloaded with the program during install.
They are used for writing vim plugins in Python. They are not required for normal operation.
They are also unrelated to your problem; check the value of %PATH% to see if python.exe is accessible.
I just updated R from version 2.15.1 to version 3.0.0 on my MAC running 10.6.8 and now R crashes on startup.
I get the error:
Error in getLoadedDLLs() : there is no .Internal function 'getLoadedDLLs'
Error in checkConflicts(value) :
".isMethodsDispatchOn" is not a BUILTIN function
Any ideas on how to go about?
The most common cause of this is having a corrupted ".Rdata" file in your working directory. Using the Mac Finder.app you will not by default be able to see files that begin with a ".", so-called dotfiles. Those files can be "seen" if you execute a change to the plist controlling the behavior of Finder.app. Open a Terminal.app window and run this bit of code:
defaults write com.apple.Finder AppleShowAllFiles YES
Then /point/-/click/-/hold/ on Dock-Finder-icon, and choose "Relaunch"
If you to do so, you can then change it back with the obvious modfication to that procedure. I happen to like seeing the hidden files so that's the way I run my Mac all the time, but some people may feel it is too dangerous to expose the "hidden secrets" to their own bumbling.
Paul raises a good point: I run the following R function in the R console after updating:
update.packages(checkBuilt=TRUE, ask=FALSE)
I have a lot of installed packages and paging through the entire list has gotten too tiresome so I bypass the ask-messages. Sometimes you will get errors because there may be dependencies on r-forge or Omegahat packages or on packages that need to be compiled from source. These may need to be updated "by hand". And you may need more than one pass through such an effort. Take notes of which packages are missing and fill them in.
I had the same problem running RKWard on ubuntu 12.04.
Check your r-base-core, like Paul suggested, to make sure the version is also at the latest version. Mine didn't update automatically. I had a platform dependent version, but RKWard was calling the new version. To solve this problem, I simply marked r-base-core for removal and reinstalled the latest version or r-base-core. poof problem fixed, bippity boppity boo!
I suspect that your error is similar to mine because I had also JUST updated RKWard. Start at updating r-base-core or try to get all of the dependencies to match up the versions.
I hope that you can translate this into what to do on a MAC,
SU