Red Hat Bugzilla – Bug 118121
wxPython fails to build against gtk2-2.3.6-1
Last modified: 2007-11-30 17:10:38 EST
Description of problem:
# rpmbuild --rebuild wxPythonGTK2-py2.3-18.104.22.168-1.src.rpm
[happily compiles away for several minutes, then...]
+ c++ -L/usr/src/redhat/BUILD/wxPythonSrc-22.214.171.124/build/lib -pthread
-Wl,-rpath -Wl,/usr/lib/wxPython-126.96.36.199/lib -lwx_gtk2ud-2.4 wxrc.o
xml.o xmlparse.o xmlres.o xmlrole.o xmltok.o -o wxrc
undefined reference to `_gtk_accel_group_detach'
undefined reference to `_gtk_accel_group_attach'
undefined reference to `_gtk_rc_context_get_default_font_name'
collect2: ld returned 1 exit status
Honestly, I don't know if this is a problem in the gtk2 package, or
an api change in gtk2 that means wxPython needs to be modified, or
what... just wanted to bring it to the attention of someone who
Version-Release number of selected component (if applicable):
* wxPythonGTK2-py2.3-188.8.131.52-1.src.rpm from
* gtk2-2.3.6-1 from fedora rawhide
* building with gcc-3.3.3-2.1, rpm-4.3-0.19, etc from fedora rawhide
Forgot to mention that wxPython did successfully build against an
earlier rawhide gtk2, don't remember exactly but probably the
gtk2-2.3.2-2.i386.rpm that was in the FC2T1 release.
Looks like the wxGtk sources are accessing internal private
GTK+ symbols like _gtk_accel_group_detach.
there was a bug in a couple of versions of GTK+ where we
accidentally exported these symbols on Linux, but it's never been
legal to access them.
From the GTK+ README file:
* The GTK+ libraries use an '_' prefix to indicate private symbols that
must not be used by applications. On some platforms, symbols beginning
with prefixes such as _gtk, _gdk, and _pango will be exported
from the library, on others not. In no case can applications
use these private symbols.