wxPython is highly dependent upon wxGTK... Upgrading wxGTK breaks wxPython. There are two solutions: A. Have wxPython use its own private copy of wxGTK (which is actually what wxPython ppl now recommend I think...) B. Make sure wxPython is updated with wxGTK in portage.. (adding a comment to that effect to the wxGTK/Python ebuilds would be nice) I would clearly prefer B...
yes... it appears that our copy of wxGTK 2.3.4 was marked stable and wxPython wasn't upgraded in conjunction. I am working on it right now. I'll let you know if the updated version of wxPython appears to work well...
I am having trouble with wxPython 2.3.4.1 and 2.3.4.2 as well with wxGTK- 2.3.4... More testing will be done. I'll post here as I get more results. Currently things are failing on this... gcc -DNDEBUG -fPIC -DSWIG_GLOBAL -DHAVE_CONFIG_H -DWXP_USE_THREAD=1 -Isrc - I/usr/include/python2.2 -c src/gtk/misc2.cpp -o build/temp.linux-i686- 2.2/src/gtk/misc2.o -I/usr/lib/wx/include/gtk-2.3 -DGTK_NO_CHECK_CASTS - D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -I/usr/include/gtk-1.2 - I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -UNDEBUG - O2 -mcpu=i686 -pipe /usr/include/wx/utils.h: In function `PyObject* _wrap_wxSafeYield(PyObject*, PyObject*, PyObject*)': /usr/include/wx/utils.h:373: too many arguments to function `bool wxSafeYield (wxWindow* = 0)' src/gtk/misc2.cpp:1524: at this point in file error: command 'gcc' failed with exit status 1
that was my fault ... could you add your ebuilds for wxPython to cvs so i can mess around with them too ?
I have just added wxGTK-2.4.0 to portage and i am anxiously awaiting wxPython 2.4.0.?... I am not sure why wxPython is failing to compile in the 2.3.4.? series...I will post here as I make headway.
wxPython documentation says it needs to be in the exact same version as wxGTK.
already a known fact which is why the initial unmasking of wxGTK-2.3.4 was a detrimental move.
wxPython 2.4.0.1 is now out.. It would be a good time to update the ebuild...
I just tried to emerge net-p2p/pysoulseek, but dev-python/wxPython-2.4.0.1 fails to build on my system. I have wxGTK 2.4.0 installed. Here is the output: <snip> gcc -DNDEBUG -fPIC -DSWIG_GLOBAL -DHAVE_CONFIG_H -DWXP_USE_THREAD=1 -Isrc -I/usr/include/python2.2 -c src/gtk/cmndlgs.cpp -o build/temp.linux-i686-2.2/src/gtk/cmndlgs.o -I/usr/lib/wx/include/gtk-2.4 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -UNDEBUG -march=i586 -mcpu=i686 -O2 -pipe -fomit-frame-pointer -frename-registers gcc -DNDEBUG -fPIC -DSWIG_GLOBAL -DHAVE_CONFIG_H -DWXP_USE_THREAD=1 -Isrc -I/usr/include/python2.2 -c src/gtk/stattool.cpp -o build/temp.linux-i686-2.2/src/gtk/stattool.o -I/usr/lib/wx/include/gtk-2.4 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -UNDEBUG -march=i586 -mcpu=i686 -O2 -pipe -fomit-frame-pointer -frename-registers gcc -DNDEBUG -fPIC -DSWIG_GLOBAL -DHAVE_CONFIG_H -DWXP_USE_THREAD=1 -Isrc -I/usr/include/python2.2 -c src/gtk/frames.cpp -o build/temp.linux-i686-2.2/src/gtk/frames.o -I/usr/lib/wx/include/gtk-2.4 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -UNDEBUG -march=i586 -mcpu=i686 -O2 -pipe -fomit-frame-pointer -frename-registers gcc -DNDEBUG -fPIC -DSWIG_GLOBAL -DHAVE_CONFIG_H -DWXP_USE_THREAD=1 -Isrc -I/usr/include/python2.2 -c src/gtk/image.cpp -o build/temp.linux-i686-2.2/src/gtk/image.o -I/usr/lib/wx/include/gtk-2.4 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -UNDEBUG -march=i586 -mcpu=i686 -O2 -pipe -fomit-frame-pointer -frename-registers src/gtk/image.cpp: In function `void* SwigwxTIFFHandlerTowxImageHandler(void*)': src/gtk/image.cpp:1218: `wxTIFFHandler' undeclared (first use this function) src/gtk/image.cpp:1218: (Each undeclared identifier is reported only once for each function it appears in.) src/gtk/image.cpp:1218: `src' undeclared (first use this function) src/gtk/image.cpp:1220: parse error before `)' token src/gtk/image.cpp: In function `void* SwigwxTIFFHandlerTowxObject(void*)': src/gtk/image.cpp:1228: parse error before `)' token src/gtk/image.cpp: In function `PyObject* _wrap_new_wxTIFFHandler(PyObject*, PyObject*, PyObject*)': src/gtk/image.cpp:1236: `_result' undeclared (first use this function) src/gtk/image.cpp:1245: parse error before `)' token src/gtk/image.cpp:1245: parse error before `(' token error: command 'gcc' failed with exit status 1 !!! ERROR: dev-python/wxPython-2.4.0.1 failed. !!! Function src_compile, Line 53, Exitcode 1 !!! build failed Greetings
add tiff to your use variables, re-emerge wxGTK and then wxPython...
raker: you changed the error message ? jasmin: re-emerge wxGTK with all the graphical USE variables enabled (specifically tiff)
Yeah... I got rid of the error message. Although there have been many problems related to not having enough image library support I don't think that generic error message is a good idea. Sometimes a problem may not be related to that... What I am actually thinking is making tiff/jpeg/etc required dependancies.
wxGTK-2.4.0 and wxPython-2.4.0.1 has been released into portage as stable. The dependancies in wxGTK are now set so all the image library support is installed by default.
hi there, I just emerged pysoulseek, which emerged wxPython as well. but when I start pyslsk I get the following error: <snip> You're using an old version of wxPython libraries (2.4.0). You should install wxPython 2.3.3 or newer. </snap> sorry, am I mistaken when I say that v2.4.0 actually IS newer than 2.3.3???
we dont make claims for pysoulseek's ability to code upgrade to the masked version of pysoulseek and it'll work
