-
Notifications
You must be signed in to change notification settings - Fork 252
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
Add minimum glibc version to each release #160
Comments
I don't have experience to test software across different glibc versions, but how would you figure out the minimum version with which a library is supposed to work? Lz4-java is loaded into a JVM, and I guess the JVM has stricter dependencies on a specific glibc version, so I am wondering how meaningful it is to declare a minimum glibc version for lz4-java itself. |
The minimum glibc version is defined at compile time of the libraries embedded in the jar. For example 1.4.0 has a different minimum glibc version then 1.5.1. It's the OS used to compile your jar which defines the minimum glibc version. IIRC. e.g. check under /lib64/lib-c*.so |
Otherwise, we see this error which is eaten up and defaults to the Unsafe/Safe java version:
|
ok, I've just learned I can use
In this example, 2.2.5 is the minimum version...? I'll document these in the release note. Thanks for the suggestion. |
No, minimum required is still 2.14 in your example. Here is ldd output on a centos 6.9 image for 1.4.0 and 1.5.1, where 1.4.0 will work and 1.5.1 does not due to missing required lib:
|
I see, I need more study. I'll check with a centos 6.9 image.
|
|
Added minimum glibc versions to https://github.com/lz4/lz4-java/blob/1.8.0/CHANGES.md |
Useful to add minimum glibc version to each release so we can easily verify if the right version is installed on the OS.
The text was updated successfully, but these errors were encountered: