Description of problem: The primecount package failed to build during the mass rebuild, on ppc64le only. The error message indicated an assembler problem. Rerunning the failing g++ command with -save-temps gave me this: libprimecount.so.6.0.ltrans0.s: Assembler messages: libprimecount.so.6.0.ltrans0.s:27109: Error: junk at end of line, first unrecognized character is `[' libprimecount.so.6.0.ltrans0.s:27110: Error: expected comma after "operator" lto-wrapper: fatal error: /usr/bin/g++ returned 1 exit status compilation terminated. /usr/bin/ld: error: lto-wrapper failed collect2: error: ld returned 1 exit status Lines 27109 and 27110 are: .weak operator[] .set operator[],_ZNK10primecount7PiTableixEm Version-Release number of selected component (if applicable): binutils-2.35-3.fc33.ppc64le How reproducible: Always. Steps to Reproduce: 1. fedpkg clone primecount 2. cd primecount 3. fedpkg srpm 4. On a ppc64le machine: mock -r fedora-rawhide-ppc64le --enablerepo=local --rebuild primecount-6.0-2.fc33.src.rpm Actual results: Build failure due to the assembler not being able to process "operator[]". Expected results: Successful build, like on the other architectures. Additional info:
See https://koji.fedoraproject.org/koji/buildinfo?buildID=1564806 for the mass rebuild failure.
Can you try if disabling annobin fixes this? Thanks. Would it be possible to compile this file with --save-temps and attach the resulting .ii file this bug? (Something is emitting an invalid symbol name, and it could be either a GCC bug or an annobin bug.)
It might be LTO too, so before trying -save-temps, try %define _lto_cflags %{nil} if it doesn't fix it. And indeed, annobin too.
It probably isn't annobin as that does not generate this kind of symbol.
(In reply to Jakub Jelinek from comment #3) > It might be LTO too, so before trying -save-temps, try > %define _lto_cflags %{nil} > if it doesn't fix it. And indeed, annobin too. Indeed, adding %define _lto_cflags %{nil} leads to a good build.
Created attachment 1703009 [details] File with bad symbol There are no .ii files with the symbol in question, just this .s file (compressed to appease bugzilla).
Is it possible this is an OOM problem, where the compiler process is getting killed while piping assembly to the assembler? I've seen similar error messages happen when my own packages run out of memory.
I forgot to reply here, but did on fedora-devel-list. It is possible indeed, although it seems odd that arm would not be affected if so. I have disabled LTO on ppc64le for now to work around the problem.
I am going to reassign this bug to gcc. The assembler is correct in generating an error, although its diagnosis does leave something to be desired. This is either an LTO bug (most likely) or an OOM bug in gcc, causing an invalid symbol name to be generated.
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.