[pylucene-dev] gcj garbage collector initialisation and threads

[Andi Vajda]

On Tue, 18 Jul 2006, David Fraser wrote:

>>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13212 - JNI/CNI
>>
>> Until this is supported by the GC module in libgcj (an old bug, but
>> with a intent of making it work in the future, quoting Hans Boehm, its
>> author), the usual trick is to use PyLucene.PythonThread which is a
>> subclass of python's thread class which delegates the starting of the
>> underlying OS thread to libgcj.

> Right, that's what I was trying to ask above - is the bug I quoted the
> correct bug? If so, there seems to be a patch on it that if included
> would support not having to delegating the starting of the OS thread to gcj.

This could be a fix. It is for gcc 4.1, however. I've been able to use gcc 4.1 
on Gentoo with this patch:
     http://gcc.gnu.org/ml/java/2006-03/msg00190.html
which looks similar to the one you found.

I've been able to use gcc 4.1.0 on PPC Mac OS X built with darwinports.
Other platforms I've either not tried or have failed to produce a sane 
PyLucene (one where all tests pass with make test).

So, depending on your platform, this could work. Please let us know what you 
find, which compiler version and OS you endup making this work (or fail) on.

Thanks !

Andi..