| Summary: | app-shells/bash[pgo] fails build due to missing llvm-runtimes/compiler-rt-sanitizers | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | fabolous.e05 |
| Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | fabolous.e05, kfm |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build.log
emerge --info |
||
|
Description
fabolous.e05
2024-09-02 23:26:05 UTC
Would you be so kind and attach the build.log and emerge --info? Created attachment 901952 [details]
build.log
Created attachment 901953 [details]
emerge --info
same issue occurs again for ongoing llvm version bump. I think the bash ebuild should track the used LLVM_SLOT and depend on the relative version of compiler-rt-sanitizers (In reply to fabolous.e05 from comment #4) > same issue occurs again for ongoing llvm version bump. > I think the bash ebuild should track the used LLVM_SLOT and depend on the > relative version of compiler-rt-sanitizers This can't be done without (unnecessarily) adding llvm-r1.eclass to every single ebuild which _might_ use Clang. Ultimately, it depends on what the system is using. We can add compiler-rt-sanitizers to @system on LLVM profiles, I don't think we can do much more than that. Well it's only relevant for pgo ebuilds, but i agree it seems overkill. |
