Seems to be a bit of a bug in the setup.py file for JCC, given the latest sources. I'm overriding all the config information (INCLUDES, CFLAGS, LDFLAGS) to install with Python 2.5.2 and Java 5 on Ubuntu:
setenv JCC_ARGSEP ";" setenv JCC_INCLUDES "/usr/lib/jvm/java-1.5.0-sun/include;/usr/lib/jvm/java-1.5.0-sun/include/linux" setenv JCC_LFLAGS "-L/usr/lib/jvm/java-1.5.0-sun/jre/lib/i386;-ljava;-Wl,-rpath=/usr/lib/jvm/java-1.5.0-sun/jre/lib/i386:/usr/lib/jvm/java-1.5.0-sun/jre/lib/i386/client" /usr/bin/python setup.py build /usr/bin/python setup.py install But when I look at /usr/lib/python2.5/site-packages/jcc/config.py, I see the default settings for these: INCLUDES=['/usr/lib/jvm/java-6-sun/include', '/usr/lib/jvm/java-6-sun/include/linux'] CFLAGS=['-fno-strict-aliasing'] LFLAGS=['-L/usr/lib/jvm/java-6-sun/jre/lib/i386', '-ljava', '-L/usr/lib/jvm/java-6-sun/jre/lib/i386/client', '-ljvm', '-Wl,-rpath=/usr/lib/jvm/java-6-sun/jre/lib/i386:/usr/lib/jvm/java-6-sun/jre/lib/i386/client'] Of course, when I try to 'make' PyLucene, the default (wrong) settings are used, and the compile fails. Bill _______________________________________________ pylucene-dev mailing list pylucene-dev@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
