lance-format / lance-format/lance
Introduce cargo-zigbuild i Java binding release to ensure compatibility with glibc 2.17.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
Our users may encounter issues like:
java.lang.UnsatisfiedLinkError: /tmp/liblance_jni114358945862674219.so: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /tmp/liblance_jni114358945862674219.so)
Although I believe glibc 2.28 is old enough, I still think it's valuable to support lower versions if we can do so in a convenient way. We can use cargo-zigbuild to specify the exact glibc version we want, allowing us to build on Ubuntu 24.04 while still providing compatibility with glibc 2.17.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the Java binding release configuration and the current native build workflow. Read how release artifacts are built, then investigate using cargo-zigbuild to target glibc 2.17 while building on Ubuntu 24.04. Done means the Java binding release artifacts retain compatibility with glibc 2.17 and the existing release checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, rust
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100