https://sourceware.org/bugzilla/show_bug.cgi?id=29042
--- Comment #5 from Sam James <sam at gentoo dot org> --- I suspect this is the same as an issue we've been hitting in Gentoo (https://bugs.gentoo.org/834720) which is mostly noticeable if built the previous system copy of binutils with --enable-pgo=lto (or otherwise built binutils with LTO) with an older GCC, then rebuilding with a newer different version of GCC which marks itself as having a different bitcode version. Manifests as (remains for newer versions): ``` lto1: fatal error: bytecode stream in file '/usr/lib64/binutils/x86_64-pc-linux-gnu/2.37_p1/libiberty.a' generated with LTO version 11.0 instead of the expected 11.2 compilation terminated. lto-wrapper: fatal error: x86_64-pc-linux-gnu-gcc returned 1 exit status compilation terminated. ``` I ended up hitting the same issue, just manifesting differently recently, when GCC's bitcode changed for 13. -- You are receiving this mail because: You are on the CC list for the bug.