Hi all,
I am attempting to build wxPython 2.4.0.7 from the sources.
I am getting the following error when printfw.cpp is compiled.
gcc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -DSWIG_GLOBAL -DHAVE_CONFIG_H -DWXP_USE_THREAD=1 -UNDEBUG -Isrc -I/usr/local/include/python2.2 -c src/gtk/printfw.cpp -o build-gtk2.unicode/temp.linux-i586-2.2/src/gtk/printfw.o -I/usr/lib/wxPython/lib/wx/include/gtk2ud-2.4 -I/usr/lib/wxPython/include -D__WXDEBUG__ -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/pango-1.0 -I/usr/X11R6/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include
In file included from src/gtk/printfw.cpp:62:
src/printfw.h:16: parse error before `{'
src/printfw.h: In function `void _setCallbackInfo(PyObject *, PyObject *, int = 1)':
src/printfw.h:32: `m_myInst' undeclared (first use this function)
src/printfw.h:32: (Each undeclared identifier is reported only once
src/printfw.h:32: for each function it appears in.)
src/printfw.h: At top level:
src/printfw.h:32: parse error before `private'
src/gtk/printfw.cpp:100: invalid use of undefined type `class wxPyPrintout'
src/printfw.h:16: forward declaration of `class wxPyPrintout'
src/gtk/printfw.cpp: In method `void wxPyPrintout::GetPageInfo(int *, int *, int *, int *)':
src/gtk/printfw.cpp:137: `wxPrintout' undeclared (first use this function)
src/gtk/printfw.cpp:137: parse error before `::'
src/gtk/printfw.cpp:138: confused by earlier errors, bailing out
My system is:
Mandrake 7.1 + the following packages in /usr/local
Python2.2.3
gtk+-2.2.2
Mesa-5.0.3
atk-1.2.4
pango-1.2.3
glib-2.2.2
pkgconfig-0.15.0
Distutils-1.0.2
I am performing the build as root with the following path:
/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin
gcc --version => 2.95.3
I am performing the build per README.1st.txt with flags for gtk2 and unicode. WXPREF = /usr/local/
All this on a Pentium 133 Laptop with 24 Mby + 200+MB swap.
I saw from the archives that Adrian Maier had the same problem back in April. I checked the Repository and my printfw.h file does not appear corrupted. I captured the output from the setup command and ran the gcc command separately on the command line also with no joy. That was how I captured the command and output above.
I am guessing that something is screwing up the include of printfw.h
I am betting that the cause is something either really stupid or really weird.
thanks
Linton Smith