On Thu, 10 Apr 2008, Bill Janssen wrote:
This is on CentOS 5, Python 2.5.1, 64bit machine.
I notice that when I don't have the JAVA_HOME env variable set, JCC
builds and installs just fine, but building PyLucene itself fails
because it picks up the wrong Java (the gcj pseudo-java). This seems
suboptimal; I've already told JCC where Java is, so I shouldn't have
to set JAVA_HOME.
I don't know what JAVA_HOME has to do with this. JCC doesn't use it in any
way. It's probably again the same problem as last time where there are gcj
header files that get picked up before the desired ones.
Last time, it turned out that there were some classes and headers such as
java/lang/String.h that were not generated by JCC, yet needed, so gcc was
picking up the gcj header file instead.
Are you sure that you're running the very latest of JCC that includes the
fixes we made for these problems ?
Andi..
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
