Andi Vajda schrieb:
I seem to remember you saying that you were using a 64-bit architecture. According to these compile flags, you're not. -m32 denotes a 32-bit architecture python. I'd expect to see -m64 for building a 64-bit python.
We have 32 bit and 64 bit machines here - all production servers using the latter. But my personal workstation is 32 bit only and I recompiled jcc/pylucene - the crash test case I found is the same on all architectures.
It would also be interesting to see if that problem just 'went away' if you built your own Python from sources, letting its configure do the work. Maybe some of the compiler flags in the RPM python are causing problems here. You can build your own python with --prefix 'somewhere just for you' and then rebuild JCC and PyLucene to use that Python instead. I'm afraid that it's going to take a little bit of build fiddling to isolate this problem.
Will try that, too although building my own python may take a bit longer if the "O0" workaround really works. Thanks for your answer, will do more tomorrow. fs -- Felix Schwarz Dipl.-Informatiker Gubener Str. 38 10243 Berlin Germany www.schwarz.eu - software development and consulting _______________________________________________ pylucene-dev mailing list pylucene-dev@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
