I'm using ActivePython 2.0 from http://www.activestate.com on a Debian unstable system. Debian doesn't yet have a native python2.0 package, so I thought I'd use the ActivePython in the meantime. No other python interpreters are installed on the debian box. (Even if it is technically feasible, I wanted to make sure the compiler wouldn't confuse one with another) Compilation fails with the following message: Making all in sip make[2]: Entering directory `/usr/local/src/kde/sip-2.1/sip' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/local/src/kde/sip-2.1/sip' Making all in siplib make[2]: Entering directory `/usr/local/src/kde/sip-2.1/siplib' /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -DSIP_QT_SUPPORT -I/usr/lib/qt2/include -I/usr/local/ActivePython-2.0/include/python2.0/ -O2 -c objmap.c rm -f .libs/objmap.lo gcc -DHAVE_CONFIG_H -I. -I. -I.. -DSIP_QT_SUPPORT -I/usr/lib/qt2/include -I/usr/local/ActivePython-2.0/include/python2.0/ -O2 -c -fPIC -DPIC objmap.c -o .libs/objmap.lo In file included from /usr/local/ActivePython-2.0/include/python2.0/Python.h:54, from sip.h:11, from objmap.c:9: /usr/local/ActivePython-2.0/include/python2.0/pyport.h:390: #error "LONG_BIT definition appears wrong for platform (bad gcc config?)." make[2]: *** [objmap.lo] Error 1 make[2]: Leaving directory `/usr/local/src/kde/sip-2.1/siplib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/kde/sip-2.1' make: *** [all-recursive-am] Error 2 ------------ I've added blank lines for readability (so _I_ could read it...) Thing is VeePee 1.0 seems to compile fine. (So the interpreter seems to be sane, and python2.0 doesn't work strangely so far) Any ideas? Christian Lavoie E-Mail: [EMAIL PROTECTED] UIN: 947212 _______________________________________________ PyKDE mailing list [EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
