-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Please upgrade libffi to ≥3.4.2 #1381
Comments
A first rough update can be found in PR #1383. This is not complete, but a first working version. |
Ok - ran unittests on:
All existing native libraries, with the exception of AIX, were rebuild with the new libffi. As this does not touch the binary interface, AIX should still work. I would appreciate a test, before I merge this into master. |
I can confirm that Elasticsearch successfully works with the new version built from your branch. However I'm struggling to test that it supports If you would like me to check that too, could you point me to instructions to rebuild the native code? That way I can skip the SELinux checks and force it always to use file-backed pages for its executables. I tried
|
Ah - I just noticed, that there are recipes to build on mac and windows, but not Linux - at some point that needs to be corrected. For debian/ubuntu this should work: # fetch the build dependencies for the distribution libjna-java package
apt-get build-dep -yq --force-yes libjna-java
# install the remaining required dependencies
apt-get install -yq --force-yes zip unzip libtool automake libltdl-dev texinfo |
I now also ran unittests on solaris and found no regressions. I intent to merge this the next few days. |
Change was merged to master. |
Sorry it's taken so long to get back to this - testing this turned into quite a yak-shaving exercise for various reasons. Anyway I can now confirm that with this version of JNA Elasticsearch does indeed respect the Thanks so much for doing this. Can you give us a sense of how long it'll be until the next release? |
Thank you for the check and verification! For a release: It depends if anyone asks for it and you just did. I'll look into it. |
May I second that. |
The latest
libffi
(at time of writing) adds support for specifying its temporary directory via theLIBFFI_TMPDIR
environment variable. Earlier versions only use more generally-applicable locations such asTMPDIR
andHOME
. In Elasticsearch we'd like to be able to control wherelibffi
writes its executables by settingLIBFFI_TMPDIR
rather thanTMPDIR
, because administrators of locked-down systems may prefer to keepTMPDIR
pointing somewhere that's mountednoexec
.Relates #1378 which fixes a segfault if
TMPDIR
is mountednoexec
, but doesn't solve the underlying problem thatlibffi
needs to write executables somewhere.Relates elastic/elasticsearch#77014 which tracks the changes we intend to make in Elasticsearch once JNA is using a sufficiently-recent
libffi
.The text was updated successfully, but these errors were encountered: