Re: [pylucene-dev] Build problems on OS X 10.5 Leopard
Ok, scrap that last question... make install sorted it out. duh :-) Everything seems to be working A-ok. Now I need a good starting point on how to actually _use_ lucene in a Python (Django) application. Any good tutorials I can start on? Ta for all the help. P. On Thu, May 29, 2008 at 11:36 AM, Peter MacRobert [EMAIL PROTECTED] wrote: Ok, we're getting somewhere. Step 1: remove all traces of python25 installed from ports! I just built all the stuff I need manually... no biggy. Now jcc is building the correct version (10.5) and I get a clean build on pylucene. The next step is - where do I install it to? I'm assuming I need to do something with the jars that are placed in the build/ dir, but there are no instructions in the README or INSTALL files. Thanks, Peter On Wed, May 28, 2008 at 10:37 PM, Andi Vajda [EMAIL PROTECTED] wrote: On Wed, 28 May 2008, Peter MacRobert wrote: Hi there Thanks for you responses. Glad to know I'm not suffering in silence :-) I am running the ports version of python because I need to install several other libraries from ports, e.g. ipython, py-readline, psycopg2, etc. And every time I try to install one of those packages using ports it requires the ports version of python25. I know I could get around these on an individual basis, but after a while it becomes very tiresome. I assume that I should put this somewhere: MACOSX_DEPLOYMENT_TARGET=10.5 but where? In your environment. For example, in ~/.bashrc. Or set it in your shell before starting the build: export MACOSX_DEPLOYMENT_TARGET=10.5 Please note that if the python you installed from ports was built with a different value, the build is still going to fail with an error saying that you're now mixing executables built for different targets. If you must use python from ports and must use a different value than 10.5 for MACOSX_DEPLOYMENT_TARGET then, as a workaround, you can do one of: . either force enable_shared to be False in JCC's setup.py . or remove the use of @rpath in JCC's setup.py (line 132) and instead set DYLD_LIBRARY_PATH in your environment to include the directory where libjcc.dylib is installed Andi.. ___ pylucene-dev mailing list pylucene-dev@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/pylucene-dev -- Peter MacRobert Facilitating value-added convergence by harnessing collaborative metrics. -- Peter MacRobert Facilitating value-added convergence by harnessing collaborative metrics. ___ pylucene-dev mailing list pylucene-dev@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
Re: [pylucene-dev] Build problems on OS X 10.5 Leopard
On May 29, 2008, at 3:45 AM, Peter MacRobert [EMAIL PROTECTED] wrote: Ok, scrap that last question... make install sorted it out. duh :-) Everything seems to be working A-ok. Now I need a good starting point on how to actually _use_ lucene in a Python (Django) application. Any good tutorials I can start on? There are lots of samples in the source tree. In particular, all the samples from the Lucene in Action book got ported to PyLucene. Andi.. Ta for all the help. P. On Thu, May 29, 2008 at 11:36 AM, Peter MacRobert [EMAIL PROTECTED] wrote: Ok, we're getting somewhere. Step 1: remove all traces of python25 installed from ports! I just built all the stuff I need manually... no biggy. Now jcc is building the correct version (10.5) and I get a clean build on pylucene. The next step is - where do I install it to? I'm assuming I need to do something with the jars that are placed in the build/ dir, but there are no instructions in the README or INSTALL files. Thanks, Peter On Wed, May 28, 2008 at 10:37 PM, Andi Vajda [EMAIL PROTECTED] wrote: On Wed, 28 May 2008, Peter MacRobert wrote: Hi there Thanks for you responses. Glad to know I'm not suffering in silence :-) I am running the ports version of python because I need to install several other libraries from ports, e.g. ipython, py-readline, psycopg2, etc. And every time I try to install one of those packages using ports it requires the ports version of python25. I know I could get around these on an individual basis, but after a while it becomes very tiresome. I assume that I should put this somewhere: MACOSX_DEPLOYMENT_TARGET=10.5 but where? In your environment. For example, in ~/.bashrc. Or set it in your shell before starting the build: export MACOSX_DEPLOYMENT_TARGET=10.5 Please note that if the python you installed from ports was built with a different value, the build is still going to fail with an error saying that you're now mixing executables built for different targets. If you must use python from ports and must use a different value than 10.5 for MACOSX_DEPLOYMENT_TARGET then, as a workaround, you can do one of: . either force enable_shared to be False in JCC's setup.py . or remove the use of @rpath in JCC's setup.py (line 132) and instead set DYLD_LIBRARY_PATH in your environment to include the directory where libjcc.dylib is installed Andi.. ___ pylucene-dev mailing list pylucene-dev@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/pylucene-dev -- Peter MacRobert Facilitating value-added convergence by harnessing collaborative metrics. -- Peter MacRobert Facilitating value-added convergence by harnessing collaborative metrics. ___ pylucene-dev mailing list pylucene-dev@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/pylucene-dev ___ pylucene-dev mailing list pylucene-dev@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
[pylucene-dev] Build problems on OS X 10.5 Leopard
Hi there I'm trying to build pylucene on OS X Leopard. I have python 2.5 installed via ports. I originally tried to install the egg provided by Kapil Thangavelu, but I also got the error Library not loaded: @rpath/libjcc.dylib that Oliver Eilhard got. Then I tried to build JCC from source. I checked out the latest version from trunk, and successfully built and installed jcc into site-packages. However, trying to build lucene yields the following error: ld: -rpath can only be used when targeting Mac OS X 10.5 or later The full output of the build is pasted below. Any advice would be appreciated. Peter olivia$ CC=CC make ant -Dlucene.dir=lucene-java-2.4.0-649619 Buildfile: build.xml compile: [mkdir] Created dir: /Users/petermacrobert/development/dism/jcc/build/classes [javac] Compiling 25 source files to /Users/petermacrobert/development/dism/jcc/build/classes [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. jar: [mkdir] Created dir: /Users/petermacrobert/development/dism/jcc/build/jar [jar] Building jar: /Users/petermacrobert/development/dism/jcc/build/jar/extensions.jar BUILD SUCCESSFUL Total time: 0 seconds CFLAGS= /opt/local/bin/python -m jcc --shared --jar lucene-java-2.4.0-649619/build/lucene-core-2.4.0-649619.jar --jar lucene-java-2.4.0-649619/build/contrib/snowball/lucene-snowball-2.4.0-649619.jar --jar lucene-java-2.4.0-649619/build/contrib/highlighter/lucene-highlighter-2.4.0-649619.jar --jar lucene-java-2.4.0-649619/build/contrib/analyzers/lucene-analyzers-2.4.0-649619.jar --jar lucene-java-2.4.0-649619/build/contrib/regex/lucene-regex-2.4.0-649619.jar --jar lucene-java-2.4.0-649619/build/contrib/queries/lucene-queries-2.4.0-649619.jar --jar build/jar/extensions.jar --package java.lang java.lang.System java.lang.Runtime --package java.util java.text.SimpleDateFormat --package java.io java.io.StringReader java.io.InputStreamReader java.io.FileInputStream --exclude org.apache.lucene.queryParser.Token --exclude org.apache.lucene.queryParser.TokenMgrError --exclude org.apache.lucene.queryParser.QueryParserTokenManager --exclude org.apache.lucene.queryParser.ParseException --python lucene --mapping org.apache.lucene.document.Document 'get:(Ljava/lang/String;)Ljava/lang/String;' --mapping java.util.Properties 'getProperty:(Ljava/lang/String;)Ljava/lang/String;' --sequence org.apache.lucene.search.Hits 'length:()I' 'doc:(I)Lorg/apache/lucene/document/Document;' --version 2.4.0-649619 --files 1 --build running build_ext building 'lucene._lucene' extension creating build/temp.macosx-10.3-i386-2.5 creating build/temp.macosx-10.3-i386-2.5/build creating build/temp.macosx-10.3-i386-2.5/build/_lucene CC -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DPYTHON=1 -D_jcc_shared=1 -I/System/Library/Frameworks/JavaVM.framework/Versions/Current/Headers -Ibuild/_lucene -I/opt/local/lib/python2.5/site-packages/JCC-1.9-py2.5-macosx-10.3-i386.egg/jcc/sources -I/opt/local/include/python2.5 -c build/_lucene/__init__.cpp -o build/temp.macosx-10.3-i386-2.5/build/_lucene/__init__.o -fno-strict-aliasing cc1plus: warning: command line option -Wstrict-prototypes is valid for C/ObjC but not for C++ CC -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DPYTHON=1 -D_jcc_shared=1 -I/System/Library/Frameworks/JavaVM.framework/Versions/Current/Headers -Ibuild/_lucene -I/opt/local/lib/python2.5/site-packages/JCC-1.9-py2.5-macosx-10.3-i386.egg/jcc/sources -I/opt/local/include/python2.5 -c build/_lucene/__wrap__.cpp -o build/temp.macosx-10.3-i386-2.5/build/_lucene/__wrap__.o -fno-strict-aliasing cc1plus: warning: command line option -Wstrict-prototypes is valid for C/ObjC but not for C++ CC -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DPYTHON=1 -D_jcc_shared=1 -I/System/Library/Frameworks/JavaVM.framework/Versions/Current/Headers -Ibuild/_lucene -I/opt/local/lib/python2.5/site-packages/JCC-1.9-py2.5-macosx-10.3-i386.egg/jcc/sources -I/opt/local/include/python2.5 -c build/_lucene/functions.cpp -o build/temp.macosx-10.3-i386-2.5/build/_lucene/functions.o -fno-strict-aliasing cc1plus: warning: command line option -Wstrict-prototypes is valid for C/ObjC but not for C++ CC -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DPYTHON=1 -D_jcc_shared=1 -I/System/Library/Frameworks/JavaVM.framework/Versions/Current/Headers -Ibuild/_lucene -I/opt/local/lib/python2.5/site-packages/JCC-1.9-py2.5-macosx-10.3-i386.egg/jcc/sources -I/opt/local/include/python2.5 -c build/_lucene/JObject.cpp -o build/temp.macosx-10.3-i386-2.5/build/_lucene/JObject.o -fno-strict-aliasing cc1plus: warning: command line option -Wstrict-prototypes is valid for C/ObjC but not for C++ CC -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DPYTHON=1 -D_jcc_shared=1 -I/System/Library/Frameworks/JavaVM.framework/Versions/Current/Headers -Ibuild/_lucene -I/opt/local/lib/python2.5/site-packages/JCC-1.9-py2.5-macosx-10.3-i386.egg/jcc/sources
Re: [pylucene-dev] Build problems on OS X 10.5 Leopard
On Wed, 28 May 2008, Peter MacRobert wrote: I'm trying to build pylucene on OS X Leopard. I have python 2.5 installed via ports. I originally tried to install the egg provided by Kapil Thangavelu, but I also got the error Library not loaded: @rpath/libjcc.dylib that Oliver Eilhard got. Then I tried to build JCC from source. I checked out the latest version from trunk, and successfully built and installed jcc into site-packages. However, trying to build lucene yields the following error: ld: -rpath can only be used when targeting Mac OS X 10.5 or later The full output of the build is pasted below. Any advice would be appreciated. Did you set MACOSX_DEPLOYMENT_TARGET ? It seems that your linker doesn't allow -rpath to be used when making executables that could run on Mac OS X pre-10.5. I don't know if this is a limitation of the linker in general or of the version you're using my I think that this is what this message means ? Why are you using Python 2.5 from ports instead of from Leopard ? Leopard ships with Python 2.5 pre-installed. Andi.. ___ pylucene-dev mailing list pylucene-dev@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
Re: [pylucene-dev] Build problems on OS X 10.5 Leopard
I'm trying to build pylucene on OS X Leopard. I have python 2.5 installed via ports. Python 2.5 comes pre-installed on Leopard. Why did you install another copy? ld: -rpath can only be used when targeting Mac OS X 10.5 or later I'd try building with the system Python -- the Python you installed seems to think that you're using OS X 10.3. It was probably built with that platform. Bill ___ pylucene-dev mailing list pylucene-dev@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
Re: [pylucene-dev] Build problems on OS X 10.5 Leopard
Hi there Thanks for you responses. Glad to know I'm not suffering in silence :-) I am running the ports version of python because I need to install several other libraries from ports, e.g. ipython, py-readline, psycopg2, etc. And every time I try to install one of those packages using ports it requires the ports version of python25. I know I could get around these on an individual basis, but after a while it becomes very tiresome. I assume that I should put this somewhere: MACOSX_DEPLOYMENT_TARGET=10.5 but where? Thanks, Peter On Wed, May 28, 2008 at 8:16 PM, Bill Janssen [EMAIL PROTECTED] wrote: I'm trying to build pylucene on OS X Leopard. I have python 2.5 installed via ports. Python 2.5 comes pre-installed on Leopard. Why did you install another copy? ld: -rpath can only be used when targeting Mac OS X 10.5 or later I'd try building with the system Python -- the Python you installed seems to think that you're using OS X 10.3. It was probably built with that platform. Bill ___ pylucene-dev mailing list pylucene-dev@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/pylucene-dev -- Peter MacRobert Facilitating value-added convergence by harnessing collaborative metrics. ___ pylucene-dev mailing list pylucene-dev@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
Re: [pylucene-dev] Build problems on OS X 10.5 Leopard
On Wed, 28 May 2008, Peter MacRobert wrote: Hi there Thanks for you responses. Glad to know I'm not suffering in silence :-) I am running the ports version of python because I need to install several other libraries from ports, e.g. ipython, py-readline, psycopg2, etc. And every time I try to install one of those packages using ports it requires the ports version of python25. I know I could get around these on an individual basis, but after a while it becomes very tiresome. I assume that I should put this somewhere: MACOSX_DEPLOYMENT_TARGET=10.5 but where? In your environment. For example, in ~/.bashrc. Or set it in your shell before starting the build: export MACOSX_DEPLOYMENT_TARGET=10.5 Please note that if the python you installed from ports was built with a different value, the build is still going to fail with an error saying that you're now mixing executables built for different targets. If you must use python from ports and must use a different value than 10.5 for MACOSX_DEPLOYMENT_TARGET then, as a workaround, you can do one of: . either force enable_shared to be False in JCC's setup.py . or remove the use of @rpath in JCC's setup.py (line 132) and instead set DYLD_LIBRARY_PATH in your environment to include the directory where libjcc.dylib is installed Andi.. ___ pylucene-dev mailing list pylucene-dev@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
Re: [pylucene-dev] Build problems on OS X 10.5 Leopard
I am running the ports version of python because I need to install several other libraries from ports, e.g. ipython, py-readline, psycopg2, etc. And every time I try to install one of those packages using ports it requires the ports version of python25. I know I could get around these on an individual basis, but after a while it becomes very tiresome. But the build error indicated that this suite of packages was built together on an OS X 10.3 (Panther) system. I doubt you'll be able to build new components for that suite on a 10.5 system. Bill ___ pylucene-dev mailing list pylucene-dev@osafoundation.org http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
