On Fri, 15 Feb 2008, Aijin Kim wrote:
I'm trying to build the latest pylucene with gcc(3.4.4) on Solaris(x86).
After building jcc-it was ok-I got errors as below when trying to build
pylucene:
/
build/_lucene/org/apache/lucene/analysis/Token.h:74: error: expected
unqualified-id before numeric constant
build/_lucene/org/apache/lucene/analysis/Token.h:74: error: abstract
declarator `java::lang::String*' used as declaration
build/_lucene/org/apache/lucene/analysis/Token.h:74: error: expected `;'
before numeric constant
build/_lucene/__wrap__.cpp:72662: error: expected unqualified-id before
numeric constant
build/_lucene/__wrap__.cpp:72662: error: expected init-declarator before
numeric constant
build/_lucene/__wrap__.cpp:72662: error: expected `,' or `;' before
numeric constant
build/_lucene/__wrap__.cpp: In static member function `static _jclass*
org::apache::lucene::analysis::Token::initializeClass()':
build/_lucene/__wrap__.cpp:72701: error: non-lvalue in assignment
build/_lucene/__wrap__.cpp: In static member function `static void
org::apache::lucene::analysis::t_Token::initialize(PyObject*)':
build/_lucene/__wrap__.cpp:72898: error: expected unqualified-id before
numeric constant
error: command 'gcc' failed with exit status 1
gmake: *** [compile] Error 1
/
I googled some info and it seems that the errors are specific to Solaris
x86.
However, i don't know how can I fix them.
Use the Solaris compiler instead, Sun Studio.
I recently did a build of PyLucene on Solaris 11 with the corresponding Sun
Studio C++ and it works well. The changes necessary made it into PyLucene
2.3.0.
I realize that this may be easier said that done if Python was itself
compiled with gcc on that system.
I'd much appreciate if anyone has idea on this.
Another solution would be to use a newer gcc compiler. 3.4.4 is really
really old now. How about using 4.x ?
Andi..
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
