Bug 434375 - ikvm failed massrebuild attempt for GCC 4.3
Summary: ikvm failed massrebuild attempt for GCC 4.3
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: ikvm
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Paul F. Johnson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: gcc43rebuildfail
TreeView+ depends on / blocked
 
Reported: 2008-02-22 16:06 UTC by Jesse Keating
Modified: 2013-01-10 03:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-09-05 13:56:51 UTC


Attachments (Terms of Use)

Description Jesse Keating 2008-02-22 16:06:16 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=443218
Exit code was 10, check the root.log for the failed buildArch task.

Comment 1 Jon Stanley 2008-03-01 02:39:39 UTC
scratch build 480726

Comment 2 Jon Stanley 2008-03-01 03:00:28 UTC
ppc64 no mono-devel

Comment 3 Paul F. Johnson 2008-05-11 21:00:23 UTC
ikvm is not being built from source so I'm not suprised that this doesn't build!

Comment 4 Jon Stanley 2008-05-11 23:18:15 UTC
I'm gonna reopen this for a few reasons.  

1) Binary blobs (which I note in the sources) are not allowed in Fedora - please
note the mono packaging guidelines at
http://fedoraproject.org/wiki/Packaging/Mono#head-1d3454f431ec1c8761eb46582e7f66bbddc1fd08

2) If a package is known not to build on a certain arch, then there should be an
ExclusiveArch such that builds are not attempted there.

Comment 5 Bug Zapper 2008-05-14 05:30:59 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Matt Domsch 2008-09-05 13:56:49 UTC
builds 2008-08-24


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