void-linux / void-linux/void-packages
llvm21: ftbfs: unversioned subpackages now point to llvm22
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.4k
- Forks
- 2.8k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 299
Description
Description of issue
@JkktBkkt previously attempted to package an llvm21 revbump for #59704 but they cannot pass the installation phase because libcxx, libunwind and other LLVM-related packages, with their -devel counterparts, were symlinked to llvm22. It appears as changing the symlink for those packages to llvm21 fixed the issue. However, that solution is hacky, and it was claimed to only be done for testing purposes. I believe this poses a larger issue with LLVM on Void Linux, which affects maintenance and could affect CI.
Solutions
- TBD
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
Start by reproducing the llvm21 installation phase with libcxx, libunwind, and their -devel packages. Inspect how unversioned LLVM-related package symlinks are selected and compare the llvm21 and llvm22 targets. Done means the llvm21 revbump installs without manually changing symlinks and the version-selection behavior is suitable for CI.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100