On Feb 19, 2008, at 21:17, Bill Janssen <[EMAIL PROTECTED]> wrote:
Seems like a bug somewhere in JCC. On the other hand, I was able to
build and install PyLucene with this JCC. Any idea what's going on?
Comparing the PyLucene build with my build, I see that with my build,
gcc is being passed the flag "-fno-strict-aliasing", whereas in the
PyLucene build it isn't. Wonder why not? I don't have CFLAGS set.
The latest JCC release has CFLAGS set to include that flag in
setup.py. There is no need to set it as an env var in the Makefile
anymore.
In any case, this flag is not related to the bogus jni.h problem in
your earlier message.
Andi..
Bill
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
