[pylucene-dev] About compiling with gcc 4.2

[Manuel Albela Miranda]

Manuel Albela Miranda wrote:
> Andi Vajda wrote:
>>
>> On Thu, 23 Nov 2006, Greg Kuperberg wrote:
>>
>>> On Thu, Nov 23, 2006 at 11:12:12PM -0400, David Pratt wrote:
>>>> Hi Greg, Andi has been pretty much been single-handedly helping 
>>>> everyone
>>>> on this list with very good and timely advice. I think you are a 
>>>> bit off
>>>> base with your comments. Admittedly, the compile time is long - but
>>>> PyLucene itself is real software ingenuity - and it also takes what it
>>>> takes to compile.
>>>
>>> In one respect I didn't quite say it right.  Andi personally has done
>>> a lot of great work.  Without him there may not even be any PyLucene.
>>
>> The list of people who make PyLucene possible is actually quite long:
>>     http://svn.osafoundation.org/pylucene/trunk/CREDITS
>>
>>> So Andi has done plenty and I do not by any means mean to say that he
>>> hasn't done enough.
>>>
>>> I can also concede that installation has been made harder by two things
>>> that are beyond the control of Andi or anyone else who works on 
>>> PyLucene.
>>
>> But for PyLucene proper, no one else but me is actively working on it.
>> I welcome contributions satisfying PyLucene's itch !
>>
>>> "Lucene in Action" is a pretty good book.  I learned what I needed
>>> from it.  But it is not quite excellent.  It has a pervasive
>>> gee-whiz tone that makes it harder to understand.
>>>
>>> Also, "Lucene in Action" has not been updated for Lucene 2.0 AFAIK.
>>
>> A second edition is in the works (so I hear).
>>
>> The python version of the "Lucene in Action" samples that ship with 
>> PyLucene 2.0.0 have been updated to the new Lucene API, though. Most 
>> of them them are run during 'make test'.
>>
>> Andi..
>> _______________________________________________
>> pylucene-dev mailing list
>> pylucene-dev at osafoundation.org
>> http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
>>
>>
>>
> Hi again,
>
> I have followed all the steps you told, compiling gcc-4.2 sources, but 
> the error still remains. There is no difference between the first one 
> compiled without the gcc sources (using the gcc debian package) and 
> the last try with the compilation of the gcc sources. The test fails 
> again. I tried yesterday with the gcc-3.4.5 binaries you told me and 
> with that one the compilation and test are ok, but i have again the 
> problem with the file size.
>
> If you have another idea i appreciate it, cause my ideas are exhausted.
>
> $make test
> find test -name 'test_*.py' | xargs -n 1 /usr/bin/python2.4
> Searching for: wicked
> ESearching for: wicked
> E
> ======================================================================
> ERROR: testGetBestFragmentsSimpleQuery (__main__.HighlighterTestCase)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>  File "test/test_Highlighter.py", line 81, in 
> testGetBestFragmentsSimpleQuery
>    self.doStandardHighlights()
>  File "test/test_Highlighter.py", line 103, in doStandardHighlights
>    highlighter.setTextFragmenter(SimpleFragmenter(20))
> JavaError: java.lang.OutOfMemoryError
>
> ======================================================================
> ERROR: testSimpleHighlighter (__main__.HighlighterTestCase)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>  File "test/test_Highlighter.py", line 62, in testSimpleHighlighter
>    highlighter.setTextFragmenter(SimpleFragmenter(40))
> JavaError: java.lang.OutOfMemoryError
>
> ----------------------------------------------------------------------
> Ran 2 tests in 0.055s
>
> FAILED (errors=2)
> ETesting Indexing Incremental Looping
> indexing  0
> indexing  1
> indexing  2
> indexing  3
> indexing  4
> indexing  5
> indexing  6
> indexing  7
> indexing  8
> indexing  9
> indexing  10
> indexing  11
> indexing  12
> indexing  13
> indexing  14
> indexing  15
> indexing  16
> indexing  17
> indexing  18
> indexing  19
> indexing  20
> indexing  21
> indexing  22
> indexing  23
> indexing  24
> indexing  25
> indexing  26
> indexing  27
> indexing  28
> indexing  29
> indexing  30
> indexing  31
> indexing  32
> indexing  33
> indexing  34
> indexing  35
> indexing  36
> indexing  37
> indexing  38
> indexing  39
> indexing  40
> indexing  41
> indexing  42
> indexing  43
> indexing  44
> indexing  45
> indexing  46
> indexing  47
> indexing  48
> indexing  49
> indexing  50
> indexing  51
> indexing  52
> indexing  53
> indexing  54
> indexing  55
> indexing  56
> indexing  57
> indexing  58
> indexing  59
> indexing  60
> indexing  61
> indexing  62
> indexing  63
> indexing  64
> indexing  65
> indexing  66
> indexing  67
> indexing  68
> indexing  69
> indexing  70
> indexing  71
> indexing  72
> indexing  73
> indexing  74
> indexing  75
> indexing  76
> indexing  77
> indexing  78
> indexing  79
> indexing  80
> indexing  81
> indexing  82
> indexing  83
> indexing  84
> indexing  85
> indexing  86
> indexing  87
> indexing  88
> indexing  89
> indexing  90
> indexing  91
> indexing  92
> indexing  93
> indexing  94
> indexing  95
> indexing  96
> indexing  97
> indexing  98
> indexing  99
> .xargs: /usr/bin/python2.4: terminado por la señal 6
> make: *** [test] Error 123
>
>
>
> Regards.
>
Hey Andi!!

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!!.

Thank you very much for your patient Andi.

Regards!!

-- 
Manuel Albela Miranda
3.14 Financial
Sánchez Calviño 82
15404 Ferrol - Spain
Tel: +34 981 94 87 78
Fax: +34 981 94 87 34
e-mail: albela at 3.14financial.com
http://www.3.14financial.com