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 434055 - libnl failed massrebuild attempt for GCC 4.3
Summary: libnl failed massrebuild attempt for GCC 4.3
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libnl
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: gcc43rebuildfail
TreeView+ depends on / blocked
 
Reported: 2008-02-22 13:00 UTC by Jesse Keating
Modified: 2013-01-10 02:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-22 19:31:34 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
patch to fix build break (406 bytes, patch)
2008-02-22 14:39 UTC, Neil Horman 		no flags Details | Diff
View All

Description Jesse Keating 2008-02-22 13:00:06 UTC 
This is an automatically filed bug for a failed rebuild attempt for GCC 4.3.

http://fedoraproject.org/wiki/JesseKeating/gcc43MassRebuildProposal

Please verify why this build failed and fix it.
http://koji.fedoraproject.org/koji/taskinfo?taskID=438074
Exit code was 1, check the build.log for the failed buildArch task.
Comment 1 Neil Horman 2008-02-22 14:39:31 UTC 
Created attachment 295632 [details]
patch to fix build break

looks like the mass rebuild coincided with a glibc or kernel-headers update
that either moved the definition of ULONG_MAX to limits.h, or broke the include
chain so that whatever previously pulled in limits.h no longer does. This patch
fixes it for me in a scratch build against the f9-alpha build target
Comment 2 Dan Williams 2008-02-22 19:31:34 UTC 
Thanks Neil!  Rebuilt with your patch, libnl-1.1-3.fc9
Note You need to log in before you can comment on or make changes to this bug.