ci: fix Java Linux native glibc baseline#43
Merged
XiaoHongbo-Hope merged 1 commit intoMay 25, 2026
Conversation
|
nit: would be nice to document the glibc 2.17 baseline somewhere user-facing (e.g. release notes / |
Signed-off-by: QuakeWang <wangfuzheng0814@foxmail.com>
c8c6009 to
dae4c41
Compare
|
+1 |
XiaoHongbo-Hope
pushed a commit
that referenced
this pull request
May 25, 2026
Signed-off-by: QuakeWang <wangfuzheng0814@foxmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
This updates Java native release and snapshot workflows to build Linux GNU JNI artifacts with
cargo-zigbuildusing a fixed glibc baseline:x86_64-unknown-linux-gnu.2.17aarch64-unknown-linux-gnu.2.17The workflows now also verify the generated Linux native library with
readelf --version-infoand fail if the requiredGLIBC_*version is higher thanGLIBC_2.17.Non-Linux artifacts continue to use regular
cargo build --target.Why
The previous workflows built Linux JNI libraries directly on the GitHub runner. On newer Ubuntu runners, this can produce
.soartifacts requiring newer glibc symbols, making them fail to load on common enterprise Linux distributions with older glibc versions.