rj not installing for eclipse/R Statet - eclipse

I realize there are several posts on this, so apologies if I'm breaching etiquette. In my case, I've tried several of them, and I just can't seem to get the rj issue (of having it installed properly) resolved.
I tried the CMD INSTALL recommendation and literally copied the tar file to my R executable directory
R CMD INSTALL --no-test-load rj_*.tar.gz
I used a DOS cmd window to run it, and it failed using the * notation, so I substituted the exact rj tar file name by navigating to the path...
C:\Program Files\R\R-2.12.1\bin\x64\rj_0.5.0-5.tar.gz
and running
R CMD INSTALL --no-test-load rj_0.5.0-5.tar.gz
This seemed to work as R shows all Java packages installed (inc. Rjava)
> ("rj" %in% installed.packages()[,"Package"])
[1] TRUE
> ("rJava" %in% installed.packages()[,"Package"])
[1] TRUE
>
Yet, in the eclipse environment, I'm still getting rj missing error.
Any thoughts on what to try next? I really want to get the debug capability to work here and pulling my hair out over this.
Oh, and also even though it shows installed in R. If I try to launch inside R, I get:
> library(rj)
Error : .onLoad failed in loadNamespace() for 'rj', details:
call: .jcall("de/walware/rj/server/RJ", "Lde/walware/rj/server/RJ;",
error: RcallMethod: cannot determine object class
Error: package/namespace load failed for 'rj'
Using Eclipse SDK Version: 3.8.0
StatET 3.01.02
rj_0.5.0-5

Related

Unable to open Code-insiders undefined symbol SHA256

I am currently unable to open code-insiders (latest build) The interface loads and then immediately closes, however there are code-insider processes left behind still running in back ground that I have to kill directly. The error in the log is: /usr/share/code-insiders/code-insiders --unity-launch --enable-crashpad: symbol lookup error: /usr/share/code-insiders/resources/app/node_modules.asar.unpacked/vscode-encrypt/build/Release/vscode-encrypt-native.node: undefined symbol: SHA256_Init I have seen similar posts that point to the libcrypt and libssh libraries and I have tried re-installing both with no change. I have also purged code and reinstalled the latest build. This still occurs if I try and launch with extensions disabled.
Any suggestions on where to search next would be appreciated.
SHA256_Init crash problem is due to the vscode-encrypt-native ELF is not linked against lcrypto so the symbols cannot be resolved properly.
You can do a quick fix:
$ find /usr/lib/ -type f -name "libcrypto.so.*"
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
$ sudo apt instal patchelf
$ sudo patchelf --add-needed libcrypto.so.1.1 /usr/share/code-insiders/resources/app/node_modules.asar.unpacked/vscode-encrypt/build/Release/vscode-encrypt-native.node
Ref: https://github.com/microsoft/vscode/issues/142656#issuecomment-1034173634

Trying to install SDL Perl on Windows 10, problems with "make" (and "dmake" and "gmake")

I am using Windows 10 and Strawberry Perl. I found this nice tutorial on building a 3D engine in Perl. Which requires SDL. For a couple of days I've been trying to install it, but it doesn't work. First I tried via CPAN, no success. No I am trying manually, but I am getting error messages when using "make". If I type "perl -V:make" it says I should use "dmake". If I do so, there's a dmake warning, telling me to use gmake instead. If I do that, there's the following message:
"to undefined at C:/Perl64/site/lib/ExtUtils/Install.pm line 1199. gmake: *** [Makefile:942: pm_to_blib] Error 2"
Any suggestions how to fix this? Or is there an easy (easier) way to install SDL?
It seems like the Perl SDL module uses SDL version 1.2.14, whereas the documentation says
The best course of action is to move to SDL 2.0 or later as quickly as
possible
So, I would recommend looking at the Python bindings PySDL2 instead. The following worked for me on Windows 10:
Downloaded Python 3.8 from here:
https://www.python.org/ftp/python/3.8.2/python-3.8.2-amd64.exe
Then added the following to the User enviroment variables for "Path" (NOTE: at the beginning, not at the end):
%USERPROFILE%\AppData\Local\Programs\Python\Python38
%USERPROFILE%\AppData\Local\Programs\Python\Python38\Scripts
Then, from the command prompt install pysdl2:
>pip install pysdl2
Collecting pysdl2
Downloading https://files.pythonhosted.org/packages/60/ba/ddb48261848874eeb3d54963edbf3c74fff86499746aeb23151f123953bb/PySDL2-0.9.7-py3-none-any.whl (541kB)
|████████████████████████████████| 542kB 2.2MB/s
Installing collected packages: pysdl2
Successfully installed pysdl2-0.9.7
>pip install pysdl2-dll
Collecting pysdl2-dll
Downloading https://files.pythonhosted.org/packages/01/37/f9aa5472fb85ce94507c69110916133ad29b650d2bf277de2cce37d7ad7d/pysdl2_dll-2.0.12-py2.py3-none-win_amd64.whl (2.5MB)
|████████████████████████████████| 2.5MB 3.2MB/s
Installing collected packages: pysdl2-dll
Successfully installed pysdl2-dll-2.0.12
Then, add a new User environment variable PYTHONPATH with value:
%USERPROFILE%\AppData\Local\Programs\Python\Python38\Lib\site-packages
Close the command prompt, and reopen a new one to update the environment variables. Then I created a test Python script:
import sys
import sdl2.ext
resource_dir=r'C:\Users\hakon\AppData\Local\Programs\Python\Python38\Lib\site-packages\sdl2\examples'
RESOURCES = sdl2.ext.Resources(resource_dir, "resources")
sdl2.ext.init()
window = sdl2.ext.Window("Hello World!", size=(640, 480))
window.show()
factory = sdl2.ext.SpriteFactory(sdl2.ext.SOFTWARE)
sprite = factory.from_image(RESOURCES.get_path("hello.bmp"))
spriterenderer = factory.create_sprite_render_system(window)
spriterenderer.render(sprite)
processor = sdl2.ext.TestEventProcessor()
processor.run(window)
sdl2.ext.quit()
and finally run it from the command prompt:
> python test.py

Haskell and postgresql - build error "The program pg_config is required but it could not be found."

I am currently learning haskell and just tried using postgresql as a database.
I generated my project with stack (stack new <name> -> stack setup -> stack build)
and then all I changed was adding the dependencies needed to persistent and postgresql to the
package.yaml file (under "dependencies:").
These are:
persistent
persistent-postgresql
persistent-template
This however results in a failing build with the following message:
postgresql-libpq > setup.exe: The program 'pg_config' is required but it could not be found.
postgresql-libpq >
-- While building package postgresql-libpq-0.9.4.2 using:
C:\Users\\AppData\Local\Temp\stack14388\postgresql-libpq-0.9.4.2.stack-work\dist\e626a42b\setup\setup --builddir=.stack-work\dist\e626a42b configure --user --package-db=clear --package-db=global --package-db=C:\sr\snapshots\365a3dde\pkgdb --libdir=C:\sr\snapshots\365a3dde\lib --bindir=C:\sr\snapshots\365a3dde\bin --datadir=C:\sr\snapshots\365a3dde\share --libexecdir=C:\sr\snapshots\365a3dde\libexec --sysconfdir=C:\sr\snapshots\365a3dde\etc --docdir=C:\sr\snapshots\365a3dde\doc\postgresql-libpq-0.9.4.2 --htmldir=C:\sr\snapshots\365a3dde\doc\postgresql-libpq-0.9.4.2 --haddockdir=C:\sr\snapshots\365a3dde\doc\postgresql-libpq-0.9.4.2 --dependency=Cabal=Cabal-2.4.1.0-5rQrtDcYhR2LOcYye7obEr --dependency=Win32=Win32-2.6.1.0 --dependency=base=base-4.12.0.0 --dependency=bytestring=bytestring-0.10.8.2 -f-use-pkg-config --extra-include-dirs=C:\Users\\AppData\Local\Programs\stack\x86_64-windows\msys2-20180531\mingw64\include --extra-lib-dirs=C:\Users\\AppData\Local\Programs\stack\x86_64-windows\msys2-20180531\mingw64\lib --extra-lib-dirs=C:\Users\\AppData\Local\Programs\stack\x86_64-windows\msys2-20180531\mingw64\bin --exact-configuration --ghc-option=-fhide-source-paths
Process exited with code: ExitFailure 1
Does anyone know how to resolve this issue and why it even occurs?
Do I have to install postgresql just for being able to run build the project? If so, how would you
do this in production, when the database could basically lie everywhere?
It looks like Haskell is trying to build with the PostgreSQL client shared library libpq.dll and uses pg_config at build time to determine where PostgreSQL is installed and how it was built.
That would mean that you have to install PostgreSQL on the machine where you build Haskell, including the header files, build environment or however it is called by the installer.
For running Haskell you would only need libpq.dll and the dependent shared libraries.
I solved the issue in Ubuntu with the following command:
apt install libpq-dev

ndk-build.cmd: command not found

(sorry for my bad english...)
I'm trying to build my .so library in Eclipse, with the CDT plugin. (It's an android project, with native code...)
Because I'm on windows, I replaced the build command in [Project->Properties->C/C++ build] with this one:
[absolute_path_to_android-ndk]\ndk-build.cmd V=1
But I got this message in the console:
C:\SDK\android-ndk-r8\ndk-build.cmd
Cannot run program "C:\SDK\android-ndk-r8\ndk-build.cmd": Le fichier spécifié est introuvable.
Error: Program "C:/SDK/android-ndk-r8/ndk-build.cmd" is not found in PATH
I tried with only "ndk-build.cmd" in the eclipse's build command, and the path to this command in my PATH environment variable, but I still have the same error.
In fact, I can't execute any program from the eclipse's build command.
I have no problem to build the library when I call ndk-build in cmd.exe, or in cygwin, but when I try to automate the library's build in Eclipse, it doesn't work...
Does anyone have a solution to my problem?
I found the solution by adding the NDK-path to the path variable, in the ubuntu terminal as well as in eclipse. Then I had to DELETE THE ".cmd" in "ndk-build.cmd" because the terminal says that I have no permission with this file ending.

rj error when running rj console in Eclipse using StatET plugin

I'm new to R and I use Eclipse a lot so I decided to install the StatET plugin in eclipse. Everything went smoothly except that I have the same problem as shown here...
Random true facts:
Windows XP Version 5.1.2600
Eclipse 3.6
StatET 0.9.2
I tried to install rj-0.5.2-1 from here, which is the package recommended for StatET 0.9.2. I put the tar.gz file in the same directory as R.exe and successfully installed it, here is the command line output...
H:\DATA\R\R-2.13.0\bin>R CMD INSTALL --no-test-load rj_*.tar.gz
* installing to library 'H:/DATA/R/R-2.13.0/library'
* installing *source* package 'rj' ...
** R
** inst
** preparing package for lazy loading
** help
No man pages found in package 'rj'
*** installing help indices
** building package indices ...
* DONE (rj)
H:\DATA\R\R-2.13.0\bin>
When it was done I could see the rj folder in the H:\DATA\R\R-2.13.0\library folder, so I thought it worked. However when I start Eclipse and start the RJ console I still get this error message...
[INFO] The R package 'rj' is not available, R-StatET tools cannot be initialized.
I also tried installing the rj-0.5.5-3 package since the binaries are precompiled; however, that didn't work either. I still get the same error message.
I noticed that at the bottom of the stackoverflow page I posted above that there is a post by Allan Stokes that states this error message is not true. Is this correct? How can I tell if this error message is a Eclipse/StatET bug or that my rj package is not installed properly? Any ideas?
Not sure if it is allowed to answer your own question, but I managed to get it working and I thought I'd post my solution. For some reason R was not recognizing the rj library when it was installed on my H: drive which is a portable drive, not my system drive. I uninstalled R and reinstalled it on my C: drive, which is my system drive. I installed rJava and rj just like before and in the r console I ran...
("rj" %in% installed.packages()[,"Package"])
it returned true indicating that the package was there, this command returned false when R was installed on my H: drive. I went into Eclipse/StatET and setup my R environment with the new location of R and ran RJ and there was no error. I'm not sure why this solution worked. Maybe the rj package need to be installed in a very specific manner. I don't understand why some libraries worked on the H: drive and some didn't. The rJava package would work on the H: drive and that the rj package wouldn't. Why is this? Ah well, it's working now. The info on this mailing list helped a lot...
http://lists.r-forge.r-project.org/pipermail/statet-user/2011-March/000812.html