contrib/gizmos/contrib/src/gizmos/ledctrl.cpp: In member function `void wxLEDNumberCtrl::OnPaint(wxPaintEvent&)': contrib/gizmos/contrib/src/gizmos/ledctrl.cpp:194: choosing `char wxString::operator[](int) const' over `char& wxString::operator[](unsigned int)' contrib/gizmos/contrib/src/gizmos/ledctrl.cpp:194: because worst conversion for the former is better than worst conversion for the latter contrib/gizmos/contrib/src/gizmos/ledctrl.cpp: In member function `void wxLEDNumberCtrl::RecalcInternals(const wxSize&)': contrib/gizmos/contrib/src/gizmos/ledctrl.cpp:321: warning: assignment to `int' from `double' contrib/gizmos/contrib/src/gizmos/ledctrl.cpp:321: warning: argument to `int' from `double' contrib/gizmos/contrib/src/gizmos/ledctrl.cpp:326: warning: assignment to `int' from `double' contrib/gizmos/contrib/src/gizmos/ledctrl.cpp:326: warning: argument to `int' from `double' error: command 'gcc' failed with exit status 1 have opengl in USE, using gcc3.1 with -march=pentium3 -O3 -pipe -mmmx -msse -mfpmath=sse -fomit-frame-pointer .
I am currently working on the wxPython build. I will be disabling the GIZMOS extension on the ebuild until a fix can be made. I will post on this bug report when I have an updated ebuild.
wxPython-2.3.2.1-r1 has been updated and it should now compile without error. GLCANVAS and GIZMOS extensions are now forced to not install as they are failing compiles currently. The new ebuild should be available on rsync servers within 24 hours. Please report back on this bug report if compilation was successful. When either or both of the extensions are fixed, wxPython will move to -r2 as additional support is added into the ebuild.
boa-constructor emerges fine, but fails to run without the gizmos package.
Hmmm, I get a different error (3.2, ix86): gcc -DNDEBUG -march=i686 -O3 -pipe -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.3 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_REENTRANT -fno-rtti -fno-exceptions -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -march=i686 -O3 -pipe src/gtk/image.cpp: In function `void* SwigwxTIFFHandlerTowxImageHandler(void*)': src/gtk/image.cpp:896: `wxTIFFHandler' undeclared (first use this function) src/gtk/image.cpp:896: (Each undeclared identifier is reported only once for each function it appears in.) src/gtk/image.cpp:896: `src' undeclared (first use this function) src/gtk/image.cpp:898: parse error before `)' token src/gtk/image.cpp: In function `void* SwigwxTIFFHandlerTowxObject(void*)': src/gtk/image.cpp:906: parse error before `)' token src/gtk/image.cpp: In function `PyObject* _wrap_new_wxTIFFHandler(PyObject*, PyObject*, PyObject*)': src/gtk/image.cpp:914: `_result' undeclared (first use this function) src/gtk/image.cpp:923: parse error before `)' token src/gtk/image.cpp:923: parse error before `(' token error: command 'gcc' failed with exit status 1 !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 27, Exitcode 1 !!! (no error message) !!! emerge aborting on /usr/portage/dev-python/wxPython/wxPython-2.3.2.1-r1.ebuild .
Please add tiff to your use variables. Re-emerge wxGTK and then emerge wxPython.
Worked for me :-D, thanx !
Closing bug report due to success report. It appears that it will not compile withouy tiff support. The ebuild has been updated to force tiff support.
