Created attachment 862533 [details] compressed build log when I tried to update to librsvg-2.56.0 with current dev-lang/rust-bin-1.69.0, it misscompiles: error: could not compile `quote` process didn't exit successfully: `rustc --crate-name quote --edition=2018 /var/tmp/portage/gnome-base/librsvg-2.56.0/work/cargo_home/gentoo/quote-1.0.26/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' --cfg 'feature="proc-macro"' -C metadata=664bf0b656ba133c -C extra-filename=-664bf0b656ba133c --out-dir /var/tmp/portage/gnome-base/librsvg-2.56.0/work/librsvg-2.56.0-.arm64/target/release/deps -L dependency=/var/tmp/portage/gnome-base/librsvg-2.56.0/work/librsvg-2.56.0-.arm64/target/release/deps --extern proc_macro2=/var/tmp/portage/gnome-base/librsvg-2.56.0/work/librsvg-2.56.0-.arm64/target/release/deps/libproc_macro2-9f67e97034115be2.rmeta --cap-lints allow` (signal: 11, SIGSEGV: invalid memory reference) downgrading to dev-lang/rust-bin-1.68.2-r1 solves the issue any idea whats going on there? the compressed build.log is attached
Created attachment 862534 [details] emerge --info
This looks like the compiler is crashing when building something rather than it building a binary which is broken (miscompilation). Anyway, in bug https://bugs.gentoo.org/877267#c1, I ended up fighting and eventually managed to get a backtrace out of it. I had to enable coredumps first (I did it via hacks using systemd-coredumpd outside the chroot, but you may want to try https://stackoverflow.com/a/29668405 too).
I switched to dev-lang/rust-1.69.0-r1 and had no problems whatsoever, is there anything I can do to inspect the binaries and libs and compare them to the prebuild rust-bin from upstream?
This issue is solved with current stable =rust-bin-1.71.1
