Description of problem: There is a version mismatch between gcc-epel (gcc-11.2.1-9.4.el9) and gcc on centos-stream (gcc-11.3.1-2.el9). This can cause LTO exceptions when building packages that depend on gccgo. Version-Release number of selected component (if applicable): gcc-epel-11.2.1-12.el9 Steps to Reproduce: fedpkg clone uwsgi cd uwsgi fedpkg --release epel9 mockbuild Actual results: ... lto1: fatal error: bytecode stream in file ‘/tmp/ccqibh4V.o’ generated with LTO version 11.2 instead of the expected 11.3 ... Additional info: That reference package currently builds in Koji because Koji uses a reference snapshot image from February to build EPEL packages, this might change in the following weeks.
Thanks for the report! I'm currently already building gcc-epel-11.3.1-2.el9 (started before your report) to get the version in sync due to upcoming RHEL 9 GA.
FEDORA-EPEL-NEXT-2022-903d9726ba has been submitted as an update to Fedora EPEL 9 Next. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2022-903d9726ba
FEDORA-EPEL-NEXT-2022-903d9726ba has been pushed to the Fedora EPEL 9 Next testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2022-903d9726ba See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-NEXT-2022-903d9726ba has been pushed to the Fedora EPEL 9 Next stable repository. If problem still persists, please make note of it in this bug report.