On Mar 20, 2025, at 00:07 Eli Schwartz <eschwa...@gentoo.org> wrote: > Rust doesn't depend on clang at all. The current ebuild does embed $CC > at the time you compile rust, as the default value for > > ``` > rustc -C linker=$CC > ``` > > But for the llvm profile that should be "clang" and not "clang-19". So > you probably changed this to a non-default value and then it broke. The > ebuild is buggy either way, yes...
Oh, I see. That makes sense. So now I have to figure out how $CC got set to "clang-19", since I don't think I would have done that deliberately. I'll investigate. > At no point is it expected that rust explicitly depends on any specific > compile. The solution is to make sure the default linker isn't specific > to that version in the first place. > > You can also pass -C linker=clang if you like. Portage will already do > this for rust software packaged in ::gentoo. Well, not across the board, it seems, because I became aware of the issue when dev-util/maturin failed to emerge. In the build.log (attached) we can see that some of the rustc commands use -C linker=clang but others do not, and they fail. Is that a separate bug? Thanks!
build.log
Description: Binary data
