llvm_slot_19 is being requested when I try to update rust. I set it in the package.use file and it gets ignored, yielding the same error. Is this related to the recent LLVM migration? I ran dispatch-conf. What else am I missing?
#LLVM REQUIRED\_USE flag being ignored
astral skiff
astral skiff
I've also tried setting LLVM_SLOT=19 in a few places with no luck.
pseudo prism
I've also tried setting LLVM_SLOT=19 in a few places with no luck.
Portage displays LLVM_SLOT="(-19)", somehow llvm_slot_19 is masked.
Try to force the useflag by creating a file with the package useflag in /etc/portage/profile/package.use.force/
astral skiff
Portage displays `LLVM_SLOT="(-19)"`, somehow `llvm_slot_19` is masked.
Try to f...
No luck. Something is blocking this somewhere. Do I need to update a specific migration package first? It's been a couple months since last update. I also tried USE="llvm_slot_19" emerge....
I've tried masking rust too and the world update simply hits the same error in the next package down the line.
I created the /etc/portage/package.use.force file which only contains dev-lang/rust llvm_slot_19 Also tried putting it in profile folder with same result, just in case.
pseudo prism
I created the /etc/portage/package.use.force file which only contains `dev-lang/...
You could also try to add
dev-lang/rust -llvm_slot_19
to package.use.mask
astral skiff
no change.
astral skiff
For a test, I moved the clippy option to be included and emerge/portage updates status just fine. It's just this llvm flag that's being stubborn.
astral skiff
None of the llvm_slot_## flags are being accepted. I masked the packages that need 19 and portage simply then barfs on the ones that need or might want 18 (e.g. mesa). If I set that in package.use, it gets ignored.
Where is the migration documentation for this? The google isn't giving me anything useful. If there's a change that might show up in a world update, I can't get there because @world fails on the above llvm barfing.
Do I need to take this to the forums instead of here?
pseudo prism
None of the `llvm_slot_##` flags are being accepted. I masked the packages that ...
Maybe it's masked from dispatch-conf in /etc/portage/package.use/? Otherwise no idea
<@&1223503067383730207>
summer ravine
Could it be that it's doing some kind of autodetection for llvm 19 but it's not found/installed?
wgetpaste -c 'emerge -pv llvm-core/llvm:19'
astral skiff
maybe this is something to do with the new rust mask? Though as I said above, I see the same behavior with mesa
astral skiff
silence means submit-a-bug-report?