Bug 434700 - ExcludeArch: ppc64 - can't build - Mono doesn't exist
ExcludeArch: ppc64 - can't build - Mono doesn't exist
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: log4net (Show other bugs)
rawhide
powerpc Linux
low Severity low
: ---
: ---
Assigned To: Christopher Brown
Fedora Extras Quality Assurance
: FutureFeature
Depends On: 229133
Blocks: FE-ExcludeArch-ppc64/F-ExcludeArch-ppc64
  Show dependency treegraph
 
Reported: 2008-02-24 11:58 EST by Christopher Brown
Modified: 2009-11-29 16:56 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-11-29 16:56:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Christopher Brown 2008-02-24 11:58:16 EST
log4net cannot be built on ppc64 as Mono does not exist there, using ExcludeArch...
Comment 1 Bug Zapper 2008-05-14 01:37:04 EDT
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 2 Toshio Ernie Kuratomi 2009-04-18 12:38:53 EDT
I've just built mono for ppc64 in the development branch.  (What will be F12).

Care to try building this again?
Comment 3 Christopher Brown 2009-05-02 21:49:29 EDT
Thanks Toshio. I'm still waiting on nant for ppc64 which was the original blocker for me as I recall. I just tried to scratch-build it but it is waiting on some mono stuff:

DEBUG util.py:256:  No Package Found for mono-sharpcvslib-devel
DEBUG util.py:256:  No Package Found for mono-ndoc-devel
DEBUG util.py:256:  No Package Found for mono-nunit22-devel

When this is fixed and nant is in ppc64 I can resubmit.
Comment 4 Christopher Brown 2009-11-29 16:56:33 EST
This is in F-11 and F-12. ppc64 is not a primary arch for F-13 so closing this.

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