On Thu, 6 Apr 2006, Kevin Ollivier wrote:
Out of curiosity, are you static linking libstdc++ too? I was able to do this
without problems on my FC1 machine, but then again I don't know if there's
any reason that this would be the wrong thing to do.
I was wondering about that too. I haven't done so yet but might. libstdc++ is
a lot smaller and usually installed anyway so I'm not so sure there is much
benefit. The reason it is handled like libgcj in the PyLucene build is that I
usually have to use a non systrem-installed gcc version and libstdc++ tends to
be newer (with a newer version number) than the system-installed one.
Andi..
Thanks,
Kevin
Andi..
Regards,
David
Andi Vajda wrote:
On Wed, 5 Apr 2006, Kevin Ollivier wrote:
I think I've found the root of the problem and have attached a patch
which, at least, gets rid of the segfault when running PyLucene in my
tests. Read below for more info on how I got this far. ;-)
Kevin,
This is awesome !
I got it to work in Linux by adding the classes from your patch to
_PyLucene.cpp via JvInitClass() calls.
I also followed the linking steps as described here:
http://gcc.gnu.org/wiki/Statically%20linking%20libgcj
for those less than obvious link command line arguments.
I've checked this into the PyLucene trunk. Now, onto Mac OS X where
libgcj.dylib is even huger.
Thank you so much for figuring this out !
Andi..
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
