linux binaries to supply
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 14
- Forks
- 2
- Avg merge
- 12h 42m
- Merged PRs (30d)
- 61
Description
-
Static-link MLIR/LLVM into vxc if you can. Otherwise your binary needs LLVM 22 shared libs present on the user's machine, and you've reintroduced the exact problem you're solving. If static linking is impractical, bundle the .so/.dylib files alongside and set rpath — but static is cleaner.
-
Build the Linux binary on the oldest glibc you can tolerate. A binary built on Ubuntu 24.04 won't run on 22.04 or Amazon Linux 2 due to glibc symbol versioning — and EC2 users are exactly your audience. Building inside an older container (Ubuntu 20.04) makes it run everywhere newer. Alternatively target musl for a fully static Linux binary, though that can complicate LLVM linking.
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 locating the vxc build and release workflow, then determine how LLVM is currently linked into the Linux binary. Compare static linking with bundling shared libraries and test an artifact built on an older glibc environment. Done means Linux binaries run on the stated older and newer targets without requiring separately installed LLVM libraries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, rust
- Domain
- build-system, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100