Created attachment 930399 [details] emerge --info '=dev-lang/rust-1.86.0-r2::gentoo' As the summary implies, without USE='doc' emerge doesn't fail (passes install phase). The issue did not occur with -r1 (with USE='doc'). Also, no problem emerging 1.87.0-r1 with this flag set. # emerge -pqv '=dev-lang/rust-1.86.0-r2::gentoo' [ebuild U ] dev-lang/rust-1.86.0-r2 [1.86.0-r1] USE="clippy doc rust-analyzer rust-src rustfmt system-llvm verify-sig (-big-endian) -debug -dist (-llvm-libunwind) -lto -test -wasm" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="sse2" LLVM_SLOT="(19)" LLVM_TARGETS="AMDGPU (X86) -AArch64 -ARC -ARM -AVR -BPF -CSKY -DirectX -Hexagon -Lanai -LoongArch -M68k -MSP430 -Mips -NVPTX -PowerPC -RISCV -SPIRV -Sparc -SystemZ -VE -WebAssembly -XCore -Xtensa"
Created attachment 930400 [details] build.log
At a glance, looks like the work of the bundled oniguruma in the onig-sys crate combined with gcc-15.
(In reply to Ionen Wolkens from comment #2) > At a glance, looks like the work of the bundled oniguruma in the onig-sys > crate combined with gcc-15. (albeit I was under the impression that this is supposed to be using system's oniguruma?)
(In reply to Ionen Wolkens from comment #3) > (In reply to Ionen Wolkens from comment #2) > > At a glance, looks like the work of the bundled oniguruma in the onig-sys > > crate combined with gcc-15. > (albeit I was under the impression that this is supposed to be using > system's oniguruma?) Oh, only >=rust-1.87.0 set RUSTONIG_SYSTEM_LIBONIG=1 and depend on it, that makes sense then.
