Build error with wip/kdebindings4-python (issue for Python < 2.5)
"David H. Gutteridge" <[email protected]>
| Newsgroups | gmane.os.netbsd.devel.pkgsrc.wip.general |
|---|---|
| Message-ID | <[email protected]> |
Hi all, When trying to compile wip/kdebindings4-python, I encountered the following error: [ 98%] Built target kpythonpluginfactory_automoc Scanning dependencies of target kpythonpluginfactory [ 99%] Building CXX object python/pykde4/kpythonpluginfactory/CMakeFiles/kpythonpluginfactory.dir/kpythonpluginfactory_automoc.o [100%] Building CXX object python/pykde4/kpythonpluginfactory/CMakeFiles/kpythonpluginfactory.dir/kpythonpluginfactory.o /usr/pkgsrc/wip/kdebindings4-python/work/.buildlink/include/python2.4/object.h:343: error: expected unqualified-id before ';' token /usr/pkgsrc/wip/kdebindings4-python/work/.buildlink/include/python2.4/object.h:343: error: abstract declarator 'PyObject*' used as declaration *** Error code 1 Stop. make: stopped in /usr/pkgsrc/wip/kdebindings4-python/work/kdebindings-4.2.0/_KDE_build *** Error code 1 Stop. make: stopped in /usr/pkgsrc/wip/kdebindings4-python/work/kdebindings-4.2.0/_KDE_build *** Error code 1 Stop. make: stopped in /usr/pkgsrc/wip/kdebindings4-python/work/kdebindings-4.2.0/_KDE_build *** Error code 1 Stop. make: stopped in /usr/pkgsrc/wip/kdebindings4-python *** Error code 1 Stop. make: stopped in /usr/pkgsrc/wip/kdebindings4-python This is on NetBSD 5.0_RC1/i386, with python24-2.4.5nb2. It seems this is due to an interaction with QT, according to this bug report filed with the Python developers: http://bugs.python.org/issue1086854 (In summary, this is because of name collision between QT and the Python header file in question: QT's moc preprocessor reserves extra words beyond what standard C++ specifies, including "slots", which appears as a variable name in Python's object.h. This was accounted for in Python 2.5.) I've confirmed that rebuilding against python25-2.5.2nb4 avoids this problem; everything compiles and installs successfully. So I think either the package needs to be marked as requiring Python 2.5 or above, or else there needs to be a patch to fix this issue if a user's employing an older version of Python? Regards, Dave ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword