Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1863599

Summary: gcc: FTBFS in Fedora rawhide/f33
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED NOTABUG 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
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: 2020-08-03 17:19:16 UTC Type: ---
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: 1803234    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2020-08-03 16:50:46 UTC 
gcc failed to build from source in Fedora rawhide/f33

https://koji.fedoraproject.org/koji/taskinfo?taskID=47953751


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
Please fix gcc at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
gcc will be orphaned. Before branching of Fedora 34,
gcc will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://fedoraproject.org/wiki/Fails_to_build_from_source
Comment 1 Fedora Release Engineering 2020-08-03 16:50:49 UTC 
Created attachment 1704400 [details]
build.log

file build.log too big, will only attach last 32768 bytes
Comment 2 Fedora Release Engineering 2020-08-03 16:50:51 UTC 
Created attachment 1704401 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Fedora Release Engineering 2020-08-03 16:50:52 UTC 
Created attachment 1704402 [details]
state.log
Comment 4 Florian Weimer 2020-08-03 17:19:16 UTC 
The build was terminated after 56 hours:

MVG%<JPDKIJG[@^>'`*W/3\?_Y7&@-_RKMV;^4<!*5^5?Z!_.WW+F6<7X*46J
MQ4,S-!1#@/>,_[IN:Q+C72K`1PM[5",'
EXCEPTION: [commandTimeoutExpired()]
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/mockbuild/trace_decorator.py", line 93, in trace
    result = func(*args, **kw)
  File "/usr/lib/python3.8/site-packages/mockbuild/util.py", line 772, in do_with_status
    raise commandTimeoutExpired("Timeout(%s) expired for command:\n # %s\n%s" % (timeout, command, output))
mockbuild.util.commandTimeoutExpired: Timeout(201600) expired for command:
 # bash --login -c /usr/bin/rpmbuild -bb --target s390x --nodeps /builddir/build/SPECS/gcc.spec

This is a general issue with slow s390x builds, cause unknown. (The hardware itself is *very* fast.)
Comment 5 Jakub Jelinek 2020-08-03 17:32:37 UTC 
Well, I've tried today to do a gcc scratch build and that failed, since the -flto -ffat-lto-objects flags must have been changed recently to -flto=auto -ffat-lto-objects and gcc.spec isn't prepared for that.
I'll fix that when I do another build this week with all the fixes I want in.