Bug 178663 - compat-wxPythonGTK2 doesn't build under mock/devel due to compiler errors
Summary: compat-wxPythonGTK2 doesn't build under mock/devel due to compiler errors
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: compat-wxPythonGTK2
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: FE5Target
TreeView+ depends on / blocked
 
Reported: 2006-01-23 03:50 UTC by Kevin Fenzi
Modified: 2007-11-30 22:11 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-04-20 02:40:51 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
mock build.log with compile failure (49.63 KB, text/plain)
2006-01-23 03:50 UTC, Kevin Fenzi 		no flags Details
View All

Description Kevin Fenzi 2006-01-23 03:50:52 UTC 
Description of problem:
compat-wxPythonGTK2 doesn't build under mock/devel due to compiler errors.
Possibly a missing BR, or a gcc issue. 

Full build.log from mock build attached.
Comment 1 Kevin Fenzi 2006-01-23 03:50:52 UTC 
Created attachment 123561 [details]
mock build.log with compile failure
Comment 2 Matthew Miller 2006-02-18 15:33:00 UTC 
FWIW, _regular_ wxPythonGTK2 doesn't either. I'm waiting on upstream for
wxPython 2.6.x -- see bug #163440. Ideally, the compat package will be fixed and
the current wxPythonGTK2 package could completely go away. Then, I'll add
wxPython 2.6.2.3 when it's available.
Comment 3 Matthew Miller 2006-03-31 13:19:33 UTC 
Spt -- building wxPython 2.6 in devel right now, so it'd be good to go ahead
with this soon when you get a chance.
Comment 4 Alex Lancaster 2006-04-19 14:37:21 UTC 
Looks like compat-wxPythonGTK2 hasn't yet been built on devel or FC-5.  Causes
some problems like bug #188215.
Comment 5 Alex Lancaster 2006-04-20 02:38:24 UTC 
Since compat-wxPythonGTK2 is now built on devel, I assume that this is now fixed.
Comment 6 Tom "spot" Callaway 2006-04-20 02:40:51 UTC 
Yes, I think it was a toolchain issue in devel, not a wxPython issue.
Note You need to log in before you can comment on or make changes to this bug.