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

Krys Wilken kryswilken at gmail.com
Tue May 29 18:32:51 PDT 2007

Hi Andi,

I just blindly did what the INSTALL file said.  So I got my gcj (and gcc, etc) 


I am happy to try your 3.4.6 build as soon as I get a chance.

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.

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.) :(

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.

Thanks for replying so quickly. :)


On Tuesday 29 May 2007 21:12, Andi Vajda wrote:
> On Tue, 29 May 2007, Krys Wilken wrote:
> >> On Mon, 28 May 2007, Krys Wilken wrote:
> >>> Just wanted to let you know that I have compiled Pylucene 2.1.0-2 for
> >>> Python 2.5 on Win32 and made it availalbe at:
> >>
> >> Great. Which version of gcj did you use ?
> >
> > 3.4.2, just like the INSTALL file says to do. :)
> >
> > Two questions, then:
> >
> > 1) Is there a better choice to try?
> Yes, I use a build of gcj 3.4.6 I made a while ago. It is available here:
> http://builds.osafoundation.org/compilers/windows/mingw-5.0-3.4.6.tar.bz2
> Did you build your gcj 3.4.2 for Windows yourself ? If so, how ? If not,
> where did you get it from ?
> I'd love to see a PyLucene build for Windows done on a recent gcj 4.x
> snapshot but I haven't had time to try that build. It's usually a multi-day
> effort to get a sane gcj for windows.
> > 2) Is that info sufficiently relevant that I should include it in the
> > archive file name?
> That info is very relevant because most 'strange' PyLucene bugs are
> actually gcj/libgcj/gc issues. Some gcj issues are solved in newer gcj
> releases but not all. It's definitely very relevant information and I
> wanted it to add with the link to your build I should be adding shortly on
> the PyLucene homepage.
> Andi..
> _______________________________________________
> pylucene-dev mailing list
> pylucene-dev at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/pylucene-dev

More information about the pylucene-dev mailing list