Bug 2046232

Summary: ppc64 build failure
Product: [Fedora] Fedora Reporter: Vitaly <vitaly>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: aoliva, dmalcolm, fweimer, jakub, jwakely, law, mpolacek, msebor, nickc, sipoyare, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-27 14:06:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2045391    

Description Vitaly 2022-01-26 12:58:04 UTC
Description of problem:
Can't build fmt package on ppc64le.

Version-Release number of selected component (if applicable):
gcc-12.0.1-0.2.fc36

How reproducible:
Always.

Steps to Reproduce:
1. fedpkg clone -a fmt
2. fedpkg scratch-build --arches ppc64le

Actual results:
[11/66] : && /usr/bin/g++ -fPIC -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -O2 -g -DNDEBUG  -Wl,-z,relro -Wl,--as-needed  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1 -Wl,-dT,/builddir/build/BUILD/fmt-8.1.1/.package_note-fmt-8.1.1-2.fc36.ppc64le.ld -shared -Wl,-soname,libfmt.so.8 -o libfmt.so.8.1.1 CMakeFiles/fmt.dir/src/format.cc.o CMakeFiles/fmt.dir/src/os.cc.o  -Wl,--as-needed && :
FAILED: libfmt.so.8.1.1 
: && /usr/bin/g++ -fPIC -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -O2 -g -DNDEBUG  -Wl,-z,relro -Wl,--as-needed  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1 -Wl,-dT,/builddir/build/BUILD/fmt-8.1.1/.package_note-fmt-8.1.1-2.fc36.ppc64le.ld -shared -Wl,-soname,libfmt.so.8 -o libfmt.so.8.1.1 CMakeFiles/fmt.dir/src/format.cc.o CMakeFiles/fmt.dir/src/os.cc.o  -Wl,--as-needed && :
{standard input}: Assembler messages:
{standard input}:31583: Error: junk at end of line, first unrecognized character is `('
{standard input}:31584: Error: expected comma after "operator"
{standard input}:32352: Error: junk at end of line, first unrecognized character is `('
{standard input}:32353: Error: expected comma after "operator"
make: *** [/tmp/ccBhCZt6.mk:2: /tmp/ccH9L8VO.ltrans0.ltrans.o] Error 1
lto-wrapper: fatal error: make returned 2 exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status

Expected results:
Successful build.

Additional info:

Comment 1 Zbigniew Jędrzejewski-Szmek 2022-01-27 09:31:37 UTC
I had a similar problem with dolfin. I "fixed" it by disabling lto: https://src.fedoraproject.org/rpms/dolfin/c/d4ed2010df138fcae8fb049bd1f78377172dcb9a?branch=rawhide

Comment 2 Jakub Jelinek 2022-01-27 09:52:48 UTC
Please just
koji wait-repo f36-build --build=annobin-10.51-2.fc36
and then rebuild, the above should be fixed in gcc-12.0.1-3.fc36 as I said on devel ml.

Comment 3 Zbigniew Jędrzejewski-Szmek 2022-01-27 11:08:09 UTC
Ah, good. The build is bending.

(BTW, %autorelease+%autochangelog work great with reverts. Normally, I'd want to revert the change, but
then not the release and changelog parts. Now I just did a revert and edited the commit message to explain
why I'm doing the revert, but I didn't have to touch the spec file at all. This wasn't publicized as a 
benefit of %autorelease+%autochangelog, but I think it's worth advertising a bit more.)

Comment 4 Zbigniew Jędrzejewski-Szmek 2022-01-27 13:49:53 UTC
*pending

dolfin built without issue.

I fired of a build of fmt too.

Comment 5 Fedora Update System 2022-01-27 14:03:37 UTC
FEDORA-2022-f48fe2f9c6 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f48fe2f9c6

Comment 6 Fedora Update System 2022-01-27 14:06:47 UTC
FEDORA-2022-f48fe2f9c6 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.