Bug 74921

Summary:	problem with ebuild for wxGTK 2.5.3, wxpython 2.5.3.1 and bittornado
Product:	Gentoo Linux	Reporter:	Giacomo Perale <ghepeu>
Component:	[OLD] Library	Assignee:	Gentoo net-p2p team <net-p2p>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	bentomb, flash3001, radek, wxwidgets
Priority:	High
Version:	2004.3
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Giacomo Perale 2004-12-19 03:42:05 UTC

Yesterday I recompiled wxGTK 2.5.3, wxpython and bittornado with ebuild currently in portage, and I couldn't get bittornado working because it failed with a message signaling that wxpython weren't installed or that installation was bad.
After a few attempts I found the problem: this is due to missing configure option "--enable-monolithic", removed as a fix for bug #71036. Another fix, that allowed me to build wxGTK without problem, is changing every "emake" command with "emake -j1"; when I recompiled wxGTK with this modification "--enable-monolithic" didn't cause any problem and bittornado now doesn't complain anymore (I recompiled wxpython too).

Comment 1 Rob Cakebread (RETIRED) gentoo-dev

2004-12-21 12:22:32 UTC

What version of bittornado are you talking about? Please post the output of "emerge --info"

--enable-monolithic is not necessary to build wxGTK according to its authors and will cause compiling to fail for some people.

Comment 2 Peter J. de Vrijer 2005-03-08 03:10:01 UTC

Had the same problem today.

I am using bittornado 0.3.8
wxGTK 2.4.2-r2
wxpython 2.4.2.4

I reemerged wxpython, that didn't help
I reemerged bittornado, didn't help either

I looked in emerge.log and saw that I upgraded
to gtk+ 2.6.2. earlier this week, so I reemerged wxGTK
and that did the trick. It's working fine now.

Peter

Comment 3 Giacomo Perale 2005-03-30 10:30:07 UTC

recompiling gtk+, wxGTK and wxPython worked for me too. I'm sorry but I completely  forgot this bug report.