Andi Vajda wrote: > > On Tue, 1 Aug 2006, Yura Smolsky wrote: > >> The PyLucene (2.0.0-1) that I used I was only able to get to compile >> with gcc 3.4.6. I tried numerous times to get it to compile with gcc >> 4.x.x with no luck. >> >> It seems that there is a gcc 2gb limit size issue with gcj in all 3.x.x >> versions and was not fixed until gcc 4.x. >> >> here is a reference >> http://lists.osafoundation.org/pipermail/pylucene-dev/2006-March/000933.html >> >> >> My point is, i dont see how to get PyLucene 2.0.0.-1 and a later 4.x >> version of gcc on a debian or fedora box. I attempted to get this to >> compile for two weeks at the beginning of this month and had no luck. > > Yes, this is a known problem. > > I've been able to use gcj 4.1.0 on gentoo linux with a patch. I suspect > it would work just as well on any Linux such as Debian or Ubuntu. > > I applied the patch as described in this message: > http://gcc.gnu.org/ml/java/2006-03/msg00190.html > > It seems, though, that this patch was superceded by the patch in bug 13212: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13212 > but I haven't tried it yet. > > > If this doesn't solve the gcj 4.x on non Red Hat Linux problem you then > have two options: > > 1. dig deeper into finding why gcj 4.x doesn't work on non Red Hat Linux > and get help from [EMAIL PROTECTED] (this is how I got the first patch > mentioned above) > > or > > 2. implement an FSDirectory in python. For an example, see the > Test_PythonDirectory.py unit tests. I don't expect python to have the > same 2gb file size limit.
Hi Andi,
I just tried the patch you mentioned with a gcc-4.1.0 and gcc-4.1.1
Note, I'm under Fedora core 5 ::
[EMAIL PROTECTED] src]# uname -a
Linux localhost.localdomain 2.6.17-1.2174_FC5 #1 Tue Aug 8 15:30:55
EDT 2006 i686 i686 i386 GNU/Linux
but I'm not using the builtin redhat gccs that actually works !
The patch does apply well on the gcc source using the release tarballs
for both gcc-version but when launching the PyLucene tests with both
1.9.1 and 2.0.0-1, with both versions of the gcc above, I got the
following warnings :
GC Warning: Repeated allocation of very large block (appr. size 512000):
May lead to memory leak and poor performance.
GC Warning: Repeated allocation of very large block (appr. size 512000):
May lead to memory leak and poor performance.
GC Warning: Repeated allocation of very large block (appr. size 512000):
May lead to memory leak and poor performance.
[...]
It's leaking big time, as the warning log says, and soon consume all the
memory and start swapping.
The patch does seem to work well as the process is not killed as soon as
the GC kicks.
Note, with PyLucene 2 I tried both static and non static build.
Am I missing something here ?
Should I try out a 4.2.x snapshot ?
Thanks !
J.
--
Julien Anguenot | Nuxeo R&D (Paris, France)
Open Source ECM - www.nuxeo.com
CPS Platform - http://www.cps-project.org
Mobile: +33 (0) 6 72 57 57 66
signature.asc
Description: OpenPGP digital signature
_______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
