Bug 914019 - gcl: FTBFS in rawhide
Summary: gcl: FTBFS in rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gcl
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jerry James
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 914432 (view as bug list)
Depends On:
Blocks: F19FTBFS
TreeView+ depends on / blocked
 
Reported: 2013-02-22 09:24 UTC by Dennis Gilmore
Modified: 2013-03-23 20:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-23 20:08:56 UTC


Attachments (Terms of Use)

Description Dennis Gilmore 2013-02-22 09:24:53 UTC
Your package gcl failed to build from source in current rawhide.

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

Build logs:
root.log: http://kojipkgs.fedoraproject.org/work/tasks/1530/4961530/root.log
build.log: http://kojipkgs.fedoraproject.org/work/tasks/1530/4961530/build.log
state.log: http://kojipkgs.fedoraproject.org/work/tasks/1530/4961530/state.log
NOTE: build logs are cleaned up after 1 week

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild

Comment 1 Jerry James 2013-02-23 17:37:38 UTC
*** Bug 914432 has been marked as a duplicate of this bug. ***

Comment 2 Jerry James 2013-02-23 17:38:59 UTC
The gcl package has consistently built successfully in mock for me, ever since the mass rebuild.  It also consistently fails to build on the koji builders, complaining about memory corruption.  I don't yet know what is different about the koji builders that could cause this.

Comment 3 Jerry James 2013-02-24 04:32:58 UTC
No, that's not right.  What is *really* going on is that the build succeeds on x86_64 (which is what I've been building in mock), but fails on i386.  The same thing happened with gmp-ecm, and that turned out to be due to changes in GMP 5.1.  Since GCL built successfully in mid-January, before GMP 5.1 was imported to Rawhide, it seems plausible that some adjustment needs to be made to the GMP-using code in GCL.  I will try to track it down.

Comment 4 Jerry James 2013-03-23 03:48:40 UTC
It turns out that adding -fno-omit-frame-pointer "fixes" the i386 build.  I still don't know why that is, but it has nothing to do with GMP.  Without that option, the value stack overflows, stomping all over any memory in its path.  I'll do a build tonight with that option, and work with upstream to discover why it is necessary.


Note You need to log in before you can comment on or make changes to this bug.