On Fri, 24 Nov 2006, Manuel Albela Miranda wrote:
I think the problem is solved....i have compiled and tested PyLucene without
any error, and now i can manage my >4gb index. The problem was that i didn't
follow all the steps, and using the svn version of PyLucene it works
perfectly, so if anyone has a similar problem, follow exactly the steps that
Andi set in the mail list, it takes a long time to compile gcc-4.2 but it
works!!.
Excellent, so you've reproduced the problem I've seen with the .jar files I
upload with the PyLucene source tarballs. These .jar files are built on a PPC
Mac OS X Powerbook G4 using Apple's Java and they've been working fine for all
other platforms where gcj 3.4.x is supported.
I first noticed that this wasn't the case with Intel Mac OS X where there is
no gcj 3.4.x. The first gcj that is functional there (heavily patched) is gcj
4.0.2. Since gcj 4.x started working well enough to be used with PyLucene
though, I've noticed that these .jar files can't be used with it.
I tried producing the .jar files on Intel Mac OS X instead, and the same
problem happens the other way: compiling PyLucene with gcj 3.4.x produces a
non functional PyLucene.
One might ask why there are .jar files in the PyLucene source tarball to begin
with. Well, at the beginning, I was trying to use gcj to compile PyLucene from
the Lucene Java sources and ended up with a large number of patches (14 and
growing) because of a number of bugs in the gcj Java front-end.
It turned out that compiling PyLucene from .class files instead was a lot
easier and more reliable. Java being 'compile once, run anywhere', I thought
that using a different Java compiler such as Apple's, Sun's or Blackdown's (on
Gentoo Linux) should not be a problem. This approach has proven correct until
I started using gcj 4.x.
There are two recent developments that may make this issue moot in the rather
near future:
- Sun's Java was recently open sourced under the GPL making its use less
controversial on some platforms such as Debian. Making PyLucene depend
on it for compilation may be realistic now. It sure has become very easy
to do on Ubuntu as outlined here [1].
- The Eclipse Java Compiler, ecj, is being worked into the gcj codebase to
serve as the next front-end to give gcj Java 1.5 support. If ecj proves
capable of compiling the Java Lucene sources to .class files without
heavily patching the Java Lucene sources first, there wouldn't be any need
to pre-compile the .java files with another package first either.
Anyway, I'm glad you've got it to work, Manuel.
Thank you for the perseverance !
Andi..
[1]
http://lists.osafoundation.org/pipermail/pylucene-dev/2006-November/001404.html
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
