Bug 1676295

Summary: flint: FTBFS in Fedora rawhide/f30
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: flintAssignee: Paulo Andrade <paulo.cesar.pereira.de.andrade>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: cse.cem+redhatbugz, loganjerry, paulo.cesar.pereira.de.andrade
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: flint-2.5.2-26.fc30 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-17 01:04:15 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: 1674516    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2019-02-11 22:31:04 UTC 
flint failed to build from source in Fedora rawhide/f30

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
Please fix flint 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,
flint will be orphaned. Before branching of Fedora 31,
flint 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 2019-02-11 22:31:08 UTC 
Created attachment 1533817 [details]
build.log

file build.log too big, will only attach last 1024 bytes
Comment 2 Fedora Release Engineering 2019-02-11 22:31:10 UTC 
Created attachment 1533818 [details]
root.log

file root.log too big, will only attach last 1024 bytes
Comment 3 Fedora Release Engineering 2019-02-11 22:31:11 UTC 
Created attachment 1533819 [details]
state.log
Comment 4 Jerry James 2019-03-03 04:46:12 UTC 
Here is what I know so far:
- If built with -O2 -fstack-protector-strong, one test fails on ppc64le.
- If built with -O2 -fstack-protector, that test passes.
- If built with -O2 -fstack-protector -fno-strict-aliasing, that test passes.
- The -Wstrict-aliasing flag, in combination with any of the above, issues no warnings.

Whether there is actually illegal aliasing going on or not is still unknown.  The investigation continues...
Comment 5 Jerry James 2019-03-04 20:57:22 UTC 
This may be a duplicate of bug 1555151.  As in that bug, the test fails because of an uninitialized value.  Also, building with -O2 -fstack-protector-strong -fno-tree-sra succeeds.  It is a different test case from that bug, and a different architecture, and didn't show up until gcc 9, but the fact that -fno-tree-sra fixes the test is suspicious.
Comment 6 Fedora Update System 2019-05-08 13:57:25 UTC 
flint-2.5.2-26.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-e1c2beea03
Comment 7 Fedora Update System 2019-05-09 02:18:13 UTC 
flint-2.5.2-26.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-e1c2beea03
Comment 8 Fedora Update System 2019-05-17 01:04:15 UTC 
flint-2.5.2-26.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.