On Tue, 6 Mar 2007, Jarek Zgoda wrote:
Hardcoding these headers in java.cpp did not help, the tests fail in the same
manner and in the same place.
Yes, there is more to it than just adding the missing classes.
What 'more' is unclear. Getting help in that area from the [EMAIL PROTECTED]
mailing list has been fruitless so far.
I am stuck. As the Debian Etch is somehow similar to Ubuntu, I'll try with
PyLucene 2.1 compiled for Dapper. So far I was even unable to compile GCJ on
my main target platform, the 64-bit CentOS, so now I'm preparing for the long
session on PITA, as there's no 64-bit PyLucene 2.1 available for download
yet...
I just upload a 64-bit PyLucene 2.1 build made with the same gcj 4.2.0
snapshot - I know, not so recent anymore :) - on Ubuntu Egdy 64 6.10.
(see http://downloads.osafoundation.org/PyLucene/linux/ubuntu64/)
If you *must* use a PyLucene.so that is statically linked with libgcj.a, I'd
suggest sticking with gcj 3.4.6 (I'm not sure this exists for 64-bit). Using a
_PyLucene.so that dynamically linked with libgcj.so works fine with recent gcj
4.2 snapshots.
As for 'CentOS' and 'PITA', pardon my ignorance, what are these things ?
For gcj support on exotic operating systems, the [EMAIL PROTECTED] mailing list
can help you with porting gcj...
Andi..
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
