Bug 1106712 - zorba: FTBFS in rawhide
Summary: zorba: FTBFS in rawhide
Keywords:
Status: CLOSED DUPLICATE of bug 1095292
Alias: None
Product: Fedora
Classification: Fedora
Component: zorba
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Gieseking
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F21FTBFS
TreeView+ depends on / blocked
 
Reported: 2014-06-09 17:10 UTC by Dennis Gilmore
Modified: 2014-06-22 16:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-22 16:02:04 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (4.45 MB, text/plain)
2014-06-09 17:10 UTC, Dennis Gilmore 		no flags Details
root.log (159.55 KB, text/plain)
2014-06-09 17:10 UTC, Dennis Gilmore 		no flags Details
state.log (1.06 KB, text/plain)
2014-06-09 17:10 UTC, Dennis Gilmore 		no flags Details
View All

Description Dennis Gilmore 2014-06-09 17:10:10 UTC 
Your package zorba failed to build from source in current rawhide.

http://koji.fedoraproject.org/koji/taskinfo?taskID=6978367

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild
Comment 1 Dennis Gilmore 2014-06-09 17:10:25 UTC 
Created attachment 905099 [details]
build.log
Comment 2 Dennis Gilmore 2014-06-09 17:10:28 UTC 
Created attachment 905100 [details]
root.log
Comment 3 Dennis Gilmore 2014-06-09 17:10:29 UTC 
Created attachment 905101 [details]
state.log
Comment 4 Martin Gieseking 2014-06-09 17:22:05 UTC 
This is a known issue (see bug 1095292) which seems to be related to gcc 4.9. I haven't been able to track down the issue yet. I don't quite understand what's happening there. It still looks like a bug in gcc's optimizer. The upstream developers are also working on finding the reason for the memory issues but without much success so far.
Comment 5 Martin Gieseking 2014-06-22 16:02:04 UTC 

*** This bug has been marked as a duplicate of bug 1095292 ***
Note You need to log in before you can comment on or make changes to this bug.