How should we handle glibc symbol versioning?
Open
Nobody has claimed this yet.
O-gnu
- Dominant language
- Rust
- Stars
- 2.6k
- Forks
- 1.3k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 69
Description
Ideally we should pin our glibc symbols to a specific version so that when a new version is introduced, we don't automatically jump to the latest and wind up with potentially broken behavior.
See discussion around https://github.com/rust-lang/libc/issues/4692#issuecomment-3305956240
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
No files, tests, or entry points are named. Start with the linked discussion in rust-lang/libc#4692, then investigate how glibc symbols are currently versioned and define what pinning should cover and how completion would be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100