[pylucene-dev] python2.4.3/PyLucene on FreeBSD crashes

[Edward N. Zalta]

Thanks for your message.  Here is what happens when I run "make test":

101# make test
find test -name 'test_*.py' | xargs -n 1 /usr/local/bin/python
...
----------------------------------------------------------------------
Ran 3 tests in 0.005s

OK
...Emake: *** [test] Error 1


So what does this mean?
Yours,
Ed
-------------------------------------------------------
Edward N. Zalta    http://mally.stanford.edu/zalta.html
Senior Research Scholar
CSLI/Cordura Hall              zalta at mally.stanford.edu
Stanford University                    ph. 650-723-0488
Stanford, CA 94305-4115                fx. 650-725-2166
-------------------------------------------------------


On Sep 10, 2007, at 3:13 PM, Andi Vajda wrote:

>
> On Mon, 10 Sep 2007, Edward N.Zalta wrote:
>
>> We would like to install our PyLucene-based indexing/search  
>> scripts on our mirror site, which is running FreeBSD 6.1 on an  
>> i386 box.   FreeBSD 6.1 came with gcc-3.4.4, but we upgraded it by  
>> compiling and installing gcc-3.4.6. Python2.4.3 successfully  
>> compiled/installed under gcc-3.4.6 and passed all its tests  
>> (excluding the ncurses test, since we didn't install that module).  
>> We then successfully compiled both PyLucene 2.0.0 and 2.0.0-8.   
>> Both install and load when Python invokes our scripts requiring  
>> PyLucene.  But our script "indexer.py" crashes almost immediately  
>> after it starts to run (it reports "1693 entries found at /usr/ 
>> local/stanford/htdocs/entries" and then dies with a segmentation  
>> fault).  We have tried compiling PyLucene many different ways  
>> (adjusting its Makefile), all with the same result.
>> Then gnu debugger gives the following information:
>
> I have no experience with PyLucene on FreeBSD. Someone else on this  
> list has used it there in the past an may be able to help you more.
> However, whenever you build PyLucene yourself, the first thing to  
> do afterwards is running its tests: make test
>
> If any test fails then your build is not sane (apart from maybe,  
> sometimes, the compound file vs regular index timing test which  
> sometimes comes out lopsided).
>
> When you PyLucene build is not sane it's usually because of a bug  
> in gcj.
> Any gcj 3.4.x with x >= 2 is normally fine. On FreeBSD, however, I  
> don't know.
>
> Andi..
> _______________________________________________
> pylucene-dev mailing list
> pylucene-dev at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/pylucene-dev