-
Notifications
You must be signed in to change notification settings - Fork 78
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
Native jar artifact does not include OpenBSD build #38
Comments
@cprice404 I think we just need someone to build the so and contribute it in a PR! |
hi @headius, On OpenBSD, there currently is jruby 9.1.5.0 installed/available, providing a I basically copied that file into the puppetserver jar, and things started to work. If you are fine with me, taking that .so from that jruby version, I can create a PR against jffi. There may or may not be a problem I see with that approach:
with the next major or minor bump of libpthread, the once created .so might stop working. There is only: not sure if I can kind of can link/create the libjffi-1.2.so file against the static libpthread.a. Or do I see a problem where there is no problem? Other minor problem I want to point out, but for the time being neglectable: jruby port/packe is limited to AMD64 on OpenBSD, the comment says: "# Runtime failures on i386 in IO#pos and IO#rewind". |
see PR #43 |
This was largely fixed by #43. Any additional issues should be filed separately. |
The native jar artifacts for this project (e.g. http://repo1.maven.org/maven2/com/github/jnr/jffi/1.2.13/jffi-1.2.13-native.jar ) include
.so
files for most platforms, but not for OpenBSD.OpenBSD is mentioned in the source code in several places, and if I install JRuby on OpenBSD, I can see this file:
/usr/local/jruby/lib/jni/x86_64-OpenBSD/libjffi-1.2.so
So I'm hoping maybe this is just a minor packaging oversight?
The text was updated successfully, but these errors were encountered: