> Taking a closer look at the error you sent me earlier, it seems to me that > the correct jni.h file is picking up the wrong array.h file. So the bug is > clearly not in JCC but either in your system's setup or in jdk 1.6's jni.h > file.
Unfortunately, every Linux platform I've ever seen is infected with a gcj install. So I'd like to find out how to work around it, rather than trying to eradicate it. > I'm hoping there > is a command like the one on Ubuntu, update-java-alternative, that does this > cleanly. Otherwise, you might want to consider reinstalling gcc by excluding > gcj. Yeah, except that I don't want to devote my life to finding out how to be a sysadmin on all the various flavors of Linux. I'd rather have JCC control the build environment so that the bad gcj headers and/or libraries don't get accidentally found. > > I have a hypothesis: if you specify "--package java.lang", header > > files are generated, which are found before the gcj header files, so > > things work. If you don't, the bad gcj header files are found. I'll > > try it and report back. Sure enough, that's the difference. Adding "--package java.lang" to the "python -m jcc" line, as PyLucene does, somehow changes the gcc command line, and things compile. Bill _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
