-
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
Making jffi-s390x-Linux.jar available #49
Comments
I'm not a member of the JRuby project, but I would suggest creating not the jar, but an easy way for anyone to build a jar. For instance, a docker image (or other kind of virtualized environment) that includes qemu and s390x libraries and a script to build the jar, or some instructions on how to get a s390x emulated environment up and going. Just my 0.02 € :) |
The native portion is intentionally small and does not need to be re-built for each release. We have minimal CI only on Linux on x86_64, though I may set up an AArch64 build soon. Any help (even if temporary) maintaining CI on other platforms would be welcome :-) |
I can try to set up CI on s390x architecture. But the jar generated for s390x will be picked up automatically under archive folder? |
Hi Charles, Meanwhile can I give you the jar file for s390x and then try to setup CI so that jar file will be available for each release. |
@headius |
@gajju26 Sorry this fell through the cracks. We have CI on Travis, which is simply x64 Linux. We would love to have you build an s390x binary for us! I don't know anything about that platform though. Are you able to try building jffi? |
Hi All,
JRuby is lacking support of s390x architecture to load jffi library. When raised the following issue
jruby/jruby#4632, I came to know I can build jffi on 390x platform and upload the jar file by creating a PR. My question is, I can build the master branch and make the jar file available but how will be latest released version taken care off by the community? Do in need to upload the jar file for every release or else by providing hardware community will take care of this thing? Is there any CI is in place for this?
CC
@headius
The text was updated successfully, but these errors were encountered: