ports/56365: x11-toolkits/py-wxPython port is broken
Bram at moolenaar.net
Wed Sep 3 11:30:17 UTC 2003
The following reply was made to PR ports/56365; it has been noted by GNATS.
From: Bram Moolenaar <Bram at moolenaar.net>
To: Thomas Gellekum <Thomas.Gellekum at gmx.de>
Cc: FreeBSD-gnats-submit at FreeBSD.org
Subject: Re: ports/56365: x11-toolkits/py-wxPython port is broken
Date: Wed, 03 Sep 2003 13:25:34 +0200
Thomas Gellekum wrote:
> Bram Moolenaar <Bram at moolenaar.net> writes:
> > building 'wxc' extension
> > cc -fno-strict-aliasing -DNDEBUG -O -pipe -D_THREAD_SAFE -DTHREAD_STACK_SIZE=0x20000 -O -pipe -fPIC -DSWIG_GLOBAL -DHAVE_CONFIG_H -DWXP_USE_THREAD=1 -UNDEBUG -Isrc -I/usr/local/include/python2.3 -c src/gtk/windows.cpp -o build/temp.freebsd-4.8-RELEASE-i386-2.3/src/gtk/windows.o -I/usr/X11R6/include -I/usr/X11R6/include -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -I/usr/X11R6/include/gtk12 -I/usr/local/include/glib12 -I/usr/local/include -I/usr/X11R6/include
> > src/gtk/windows.cpp: In function `struct PyObject * _wrap_wxMenuItem_SetMenu(PyObject *, PyObject *, PyObject *)':
> > src/gtk/windows.cpp:10728: no matching function for call to `wxMenuItem::SetMenu (wxMenu *&)'
> > error: command 'cc' failed with exit status 1
> > *** Error code 1
> Just reinstall wxgtk-devel using the latest bits or apply the patch in
> wxgtk-devel/files/patch-include::wx::menuitem.h to /usr/X11R6/include/wx/menuitem.h.
Thanks for the quick reply.
I don't understand why this patch wasn't already applied, since the
wxgtk-2.4.1 port was installed. I'll attempt doing "make deinstall" and
"make install". Since the version number is the same this shouldn't be
necessary... But it appears it does help.
Then the bug is: why isn't the correct wxgtk installed? Perhaps the
version number is wrong.
Note that Robin Dunn, the author of wxPython, recommends using the wxGTK
included with wxPython instead of a separate one, with the reason that
small version differences may cause trouble. Quote:
> wxMenuItem::SetMenu was added right after the wxGTK 2.4.1 release was
> made. (I thought it was right before, but a quick look at CVS shows
> differently. It may be that CVS was tagged earlier than I what I
> expected...) Anyway, you'll need to use the wxGTK included in the
> wxPythonSrc tarball.
I tried following the instructions in README.1st.txt but didn't get
through the configure phase.
Not too long ago, a keyboard was something to make music with...
/// Bram Moolenaar -- Bram at Moolenaar.net -- http://www.Moolenaar.net \\\
/// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\
\\\ Project leader for A-A-P -- http://www.A-A-P.org ///
\\\ Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html ///
More information about the freebsd-ports-bugs