warning: build failed, waiting for other jobs to finish... ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_systemd-j3-20210611-120458 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-11.1.0 * clang version 12.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/12/bin /usr/lib/llvm/12 12.0.0 Python 3.9.5 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby30 (with Rubygems) * Available Rust versions: [1] rust-bin-1.52.1 * The following VMs are available for generation-2: The Glorious Glasgow Haskell Compilation System, version 8.10.4 HEAD of ::gentoo commit e250d8642d15eb0dab1ef8e1014609ccc3c0af9e Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Mon Jun 14 23:50:07 2021 +0000 2021-06-14 23:50:06 UTC emerge -qpvO dev-util/rustup [ebuild N ] dev-util/rustup-1.24.3 USE="-debug"
Created attachment 716208 [details] emerge-info.txt
Created attachment 716211 [details] dev-util:rustup-1.24.3:20210615-000710.log
Created attachment 716214 [details] emerge-history.txt
Created attachment 716217 [details] environment
Created attachment 716220 [details] etc.portage.tar.bz2
Created attachment 716223 [details] temp.tar.bz2
The futex facility returned an unexpected error code. error: could not compile `ripemd160` can you try without specifying codegen-units?
If I comment out RUSTFLAGS="-C codegen-units=3" in /etc/portage/env/jobs, then it works. Is =3 wrong here or in general ? (FWIW I'm under the impression that it is the equivalent to -j3 in make.conf, right ?)
not exactly, it's number of internal codegen threads, not necessarily related to CPU threads. from https://doc.rust-lang.org/rustc/codegen-options/index.html --- codegen-units This flag controls how many code generation units the crate is split into. It takes an integer greater than 0. When a crate is split into multiple codegen units, LLVM is able to process them in parallel. Increasing parallelism may speed up compile times, but may also produce slower code. Setting this to 1 may improve the performance of generated code, but may be slower to compile. The default value, if not specified, is 16 for non-incremental builds. For incremental builds the default is 256 which allows caching to be more granular. --- this option is generally not recommended to touch, crates often specify it internally taking various factors in account, like LTO. specifying 1 should always be safe and generate fastest code and use most time to compile. I see you are using rust-bin, I'll try to reproduce with it. this crash should not happen as I understand, you may have hit compiler bug. anyway, for personal systems (not tinderbox) try to avoid using codegen-units, or explicitly set to 1.
*** Bug 806809 has been marked as a duplicate of this bug. ***
