[pylucene-dev] Pylucene 2.1.0-2, Python 2.5, Win32

Andi Vajda vajda at osafoundation.org
Tue May 29 18:49:37 PDT 2007


On Tue, 29 May 2007, Krys Wilken wrote:

> I just blindly did what the INSTALL file said.  So I got my gcj (and gcc, etc)
> from:
>
> http://prdownloads.sf.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz
>
> I am happy to try your 3.4.6 build as soon as I get a chance.

Sure, no need to but if you do it, it's better since the gcj is newer.
I remember that 3.4.2 is the earliest rev that anyone should use. Newer 3.4.x 
are better. Newer 4.x are iffy. Older 3.4.x have problems.

> Maybe an update to INSTALL is in order.  I have already noticed references to
> 3.4.6 in the Makefile, so it's kind of like getting conflicting information.
> Just a thought.

Yes, that'd be good. This whole compiler business is rather hairy, 
inconsistent across platforms and a pain to maintain.

> As for a 4.x.  I have not probs trying it, but I am certainly not qualified to
> debug it and make it sane, as you say. My Java and C and compiling in general
> are very rusty.  They were all killed by a Python. ;D  (Well, no... actually
> they were killed by my agreeing to take a job maintaining other people's
> brain dead VB code.  I've probably gotten stupider because of it.) :(

No worries. Compiling gcj for Windows is really for the masochist. No point in 
trying it unless you have a special interest in doing it. I'd love for someone 
to volunteer as my pain threshhold is kind of low in the building-gcj area 
these days. GCJ on Windows isn't exactly actively maintained either.

Building gcj on Windows requires tracking down the correct build information, 
the correct people with that info, having a Linux box to cross-compile it on, 
having the time to watch gcj build, over and over as you make simple stupid 
mistakes in the many steps required to cross-compile it, and then finally 
debug it with no debugger.

> Anyway, since the gcj version info is important, I will add it to the file
> name and README_FISRT.txt file I added.  I'll let you know when it's done.
> You might want to hold off on the link until it's done.

Great, let me know when you're ready.

Andi..


More information about the pylucene-dev mailing list