https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-lang/rust-1.66.0 calls cc directly. Discovered on: amd64 (internal ref: ci) NOTE: As per QA policy, toolchain tools must not be called directly because they can cause issue in cross-compiling and because is not possible use a different CC implementation (like clang). To reproduce, please use sys-devel/gcc-config[-native-symlinks], sys-devel/binutils-config[-native-symlinks].
Created attachment 845722 [details] build.log build log and emerge --info
Error(s) that match a know pattern: = note: No such file or directory (os error 2) RuntimeError: failed to run: /var/tmp/portage/dev-lang/rust-1.66.0/work/rust-stage0/bin/cargo build --manifest-path /var/tmp/portage/dev-lang/rust-1.66.0/work/rustc-1.66.0-src/src/bootstrap/Cargo.toml --verbose --verbose --locked --frozen error: linker `cc` not found
Confirming issue is present in 1.66.1 when building on musl. Also, wow that use of "linking with" is quite confusing ... that would be "linking using `cc`" (oof). error: linking with `cc` failed: signal: 11 (SIGSEGV) (core dumped)
Linker can be set using Cargo config: https://doc.rust-lang.org/cargo/reference/config.html
*** Bug 893264 has been marked as a duplicate of this bug. ***
I'd like to add that build process do not pass user-provided CFLAGS/CXXFLAGS to bundled libssh, libgit, nghttp2.