>>> Preparing source in /var/tmp/portage/app-text/mdbook-0.4.30/work/mdBook-0.4.30 ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/app-text/mdbook-0.4.30/work/mdBook-0.4.30 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/app-text/mdbook-0.4.30/work/mdBook-0.4.30 ... * cargo build --release error: process didn't exit successfully: `rustc -vV` (signal: 11, SIGSEGV: invalid memory reference) * ERROR: app-text/mdbook-0.4.30::gentoo failed (compile phase): * cargo build failed ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_desktop_systemd-20230607-160427 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10 [2] x86_64-pc-linux-gnu-13 * clang/llvm (if any): clang version 16.0.5 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/16/bin Configuration file: /etc/clang/clang.cfg /usr/lib/llvm/16 16.0.5 Python 3.11.4 Available Rust versions: [1] rust-1.69.0 [2] rust-bin-1.70.0 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 17.0.6_p10 [openjdk-bin-17] Available Java Virtual Machines: [1] openjdk-bin-17 system-vm php cli (if any): go version go1.20.5 linux/amd64 HEAD of ::gentoo commit bf5ef12286dd41ab34d90673c2339cc5d8c69c11 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Thu Jun 8 14:33:50 2023 +0000 2023-06-08 14:33:50 UTC emerge -qpvO app-text/mdbook [ebuild N ] app-text/mdbook-0.4.30 USE="-debug -doc"
Created attachment 863572 [details] emerge-info.txt
Created attachment 863573 [details] app-text:mdbook-0.4.30:20230608-150319.log
Created attachment 863574 [details] emerge-history.txt
Created attachment 863575 [details] environment
Created attachment 863576 [details] etc.clang.tar.xz
Created attachment 863577 [details] etc.portage.tar.xz
Created attachment 863578 [details] temp.tar.xz
known rust-bin issue
Hhm, the affected rust-bin package was unkeyworded already - and most of the tinderbox images downgraded rust-bin correctly before emerging other packages. I do wonder if this package has all X-DEPEND set right ?
Nothing special here, it just uses the BDEPEND value set by the eclass and has none of its own. Albeit given it has both rusts: Available Rust versions: [1] rust-1.69.0 [2] rust-bin-1.70.0 * Maybe it thought it didn't need to downgrade rust-bin because you have rust-1.69 or something? (which satisfies the dependency)
