The futex facility returned an unexpected error code. Running `/var/tmp/portage/dev-lang/rust-1.54.0/work/rustc-1.54.0-src/build/bootstrap/debug/build/serde-8d91e3cd6c4a7400/build-script-build` error: could not compile `walkdir` Caused by: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma-j4-20210819-210003 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-11.2.0 * Python 3.9.6 Available Rust versions: (none found) HEAD of ::gentoo commit 098fbad7d32721cdb15b37d2ff106ab8e49006d1 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Thu Aug 19 21:21:41 2021 +0000 2021-08-19 21:21:38 UTC emerge -qpvO dev-lang/rust [ebuild N ] dev-lang/rust-1.54.0 USE="rustfmt -clippy -debug -doc -miri -nightly -parallel-compiler -rls -system-bootstrap -system-llvm -test -verify-sig -wasm" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="sse2" LLVM_TARGETS="(X86) -AArch64 -AMDGPU -ARM -AVR -BPF -Hexagon -Lanai -MSP430 -Mips -NVPTX -PowerPC -RISCV -Sparc -SystemZ -WebAssembly -XCore"
Created attachment 734455 [details] emerge-info.txt
Created attachment 734458 [details] dev-lang:rust-1.54.0:20210819-230639.log
Created attachment 734461 [details] emerge-history.txt
Created attachment 734464 [details] environment
Created attachment 734467 [details] etc.portage.tar.bz2
Created attachment 734470 [details] logs.tar.bz2
Created attachment 734473 [details] temp.tar.bz2
maybe another incarnation of bug 807832
I encountered this bug yesterday with dev-lang/rustc-1.58.1 (log attached). But as mentioned in bug 807832 another try after the system update had completed was successful. So not sure what caused it.
Created attachment 763250 [details] build.log of dev-lang/rust-1.58.1
opened upstream issue
(In reply to Frederik Pfautsch from comment #9) > I encountered this bug yesterday with dev-lang/rustc-1.58.1 (log attached). > But as mentioned in bug 807832 another try after the system update had > completed was successful. So not sure what caused it. do you have any extra sandboxing enabled like bubblewrap or is it just plain portage with no extra layers or oddities? can you please always paste emerge --info output? It's really helpful to see some information like libc version, sandbox version and some other stuff that helps us pinpoint the problem. still ok to paste now, assuming you did not install new sanbox/libc since =)