oxidecomputer / oxidecomputer/oxide.rs
Generated Linux release binaries may not run on systems with older glibc
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 75
- Forks
- 21
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
Our x86_64-unknown-linux-gnu release currently get built in CI on a ubuntu-20.04 image. That's often newer than whatever glibc is used by some distros like CentOS or Rocky.
This is not a new issue for building releases in CI (and there's one solution mentioned in that blog post). I also noticed we use cargo-dist which might be able to just handle this soon™?
Contributor guide
No contributing guide indexed for this repository
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
Start by inspecting the CI release configuration and how cargo-dist builds the x86_64-unknown-linux-gnu artifact on ubuntu-20.04. Review the linked glibc compatibility discussion and determine a supported build approach. Done means release binaries run on systems with older glibc, including CentOS or Rocky.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100