Is this list the appropriate place to ask questions about installing
PyLucene?

I realize there are several moving parts, and that responsibility for all
(or even most) of them is nothing to do with PyLucene. But, I thought I'd
ask.

I spent quite a bit of time yesterday trying to make things build and play
together. The last thing I tried was to co the PyLucene trunk and follow
the instructions in INSTALL on building gcc-3.4.4 from sources. I do this,
and the build goes swimmingly until it hits this:

/usr/local/gcc-4.0.2/bin/g++ -c -o release/java.o -O2  
-DPYLUCENE_VER="\"2.0.0-2\"" -DLUCENE_VER="\"2.0.0-434148\"" 
-D_WITH_DB_DIRECTORY=1 -DDB_LIB_VER="\"4.4\"" -DDB_VER=44 
-I/usr/local/BerkeleyDB.4.4/include 
-I/Users/terry/s/svn/PyLucene/trunk/db-4.4.20 
-I/Users/terry/s/svn/PyLucene/trunk/db-4.4.20/build_unix 
-Ilucene-java-2.0.0-434148/build/classes/java 
-Ilucene-java-2.0.0-434148/build/contrib/highlighter/classes/java 
-Ilucene-java-2.0.0-434148/build/contrib/snowball/classes/java 
-Ilucene-java-2.0.0-434148/build/contrib/analyzers/classes/java 
-Ilucene-java-2.0.0-434148/build/contrib/regex/classes/java -Irelease/classes 
-Ilucene-java-2.0.0-434148/build/contrib/db/bdb/classes/java 
-I/Library/Frameworks/Python.framework/Versions/2.4/Headers 
-I/usr/local/gcc-4.0.2/include java.cpp
/usr/local/gcc-4.0.2/bin/g++ -c -o release/lucene.o -O2  
-DPYLUCENE_VER="\"2.0.0-2\"" -DLUCENE_VER="\"2.0.0-434148\"" 
-D_WITH_DB_DIRECTORY=1 -DDB_LIB_VER="\"4.4\"" -DDB_VER=44 
-I/usr/local/BerkeleyDB.4.4/include 
-I/Users/terry/s/svn/PyLucene/trunk/db-4.4.20 
-I/Users/terry/s/svn/PyLucene/trunk/db-4.4.20/build_unix 
-Ilucene-java-2.0.0-434148/build/classes/java 
-Ilucene-java-2.0.0-434148/build/contrib/highlighter/classes/java 
-Ilucene-java-2.0.0-434148/build/contrib/snowball/classes/java 
-Ilucene-java-2.0.0-434148/build/contrib/analyzers/classes/java 
-Ilucene-java-2.0.0-434148/build/contrib/regex/classes/java -Irelease/classes 
-Ilucene-java-2.0.0-434148/build/contrib/db/bdb/classes/java 
-I/Library/Frameworks/Python.framework/Versions/2.4/Headers 
-I/usr/local/gcc-4.0.2/include lucene.cpp
/usr/local/BerkeleyDB.4.4/include/db.h:1376: error: 'u_int' does not name a type
/usr/local/BerkeleyDB.4.4/include/db.h:1742: error: 'u_int' does not name a type
/usr/local/BerkeleyDB.4.4/include/db.h:1930: error: 'u_int' does not name a type
/usr/local/BerkeleyDB.4.4/include/db.h:1931: error: 'u_int' does not name a type
/usr/local/BerkeleyDB.4.4/include/db.h:1951: error: 'u_int' does not name a type
/usr/local/BerkeleyDB.4.4/include/db.h:2016: error: 'u_int' does not name a type
/usr/local/BerkeleyDB.4.4/include/db.h:2063: error: ISO C++ forbids declaration 
of 'u_long' with no type
/usr/local/BerkeleyDB.4.4/include/db.h:2063: error: expected ';' before '*' 
token
/usr/local/BerkeleyDB.4.4/include/db.h:2399: error: expected primary-expression 
before 'int'
make: *** [release/lucene.o] Error 1


And looking in /usr/local/BerkeleyDB.4.4/include/db.h I see the following
empty section:

/*
 * !!!
 * Berkeley DB uses specifically sized types.  If they're not provided by
 * the system, typedef them here.
 *
 * We protect them against multiple inclusion using __BIT_TYPES_DEFINED__,
 * as does BIND and Kerberos, since we don't know for sure what #include
 * files the user is using.
 *
 * !!!
 * We also provide the standard u_int, u_long etc., if they're not provided
 * by the system.
 */
#ifndef __BIT_TYPES_DEFINED__
#define __BIT_TYPES_DEFINED__







#endif


So it looks like u_int is not defined. I could guess and define it myself,
but I thought I'd ask here to see if there's something I'm missing.

I'm on OS X 10.4.7

I'm trying to build gcc in order to then build PyLucene against BSD DB
4.4.20. The 4.3.28 version of BSD DB does not seem to be available at
sleepycat any longer. Plus I already have Python's bsddb built against
4.4.20, so I thought building PyLucene against it was the best option.

BTW, the README in the PyLucene tarballs says "To build PyLucene from
sources, please see the INSTALL file." This could be improved a little -
the INSTALL file is in svn but is not shipped in the tarballs.

Regards, and thanks for any help,
Terry
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev

Reply via email to