-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Raspberry Pi? #59
Comments
@lukehorvat I was able to get jnr-posix to load JRuby on raspi once but there was some permission issue. We unpack a native lib and we end up putting it in /tmp (jffi shared library). I was not clear on whether there is some security issues with loading .so from /tmp or no actual space on /tmp to unload it. If I put the native files into LD_LIBRARY_PATH then things loaded. |
@enebo Which native lib? |
@lukehorvat I think what is in lib/jni within our distribution ends up getting put into to /tmp. so adding lib/jni/arm-Linux/lib/jffi-1.2.so in a way if can be seen (like LD_LIBRARY_PATH) should make native load. |
Just to rule out some things. Can you tell me what It seems there's quite a few hoops to jump through to get full native ffi support on some of these platforms under Java. |
digging further into jffi makes me think I'll need to dust off my rasppi. |
|
Yup, definitely time to dust off the rasppi. |
I'm going to close this since it seems like loading problems are mostly environmental. If there's anything actionable here, let me know. |
I'm here due to jruby/jruby#3244.
It looks like jnr-posix fails to load native POSIX on Raspbian (Raspberry Pi OS), and I'm not exactly sure why. Unfortunately, I need process killing functionality, which the JavaPOSIX fallback doesn't support.
Are there any steps we can take to make it supported? Happy to lend a hand if necessary.
The text was updated successfully, but these errors were encountered: