lucene-pylucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andi Vajda <va...@apache.org>
Subject Re: [VOTE] Release PyLucene 4.4.0-1
Date Mon, 19 Aug 2013 08:46:01 GMT

On Sun, 18 Aug 2013, Taka Epsilon wrote:

> I've resolved the previous clang++ error and built PyLucene 4.4.0
> successfully on Mac 10.8.4 with the default Python. I will write about
> what's causing the issue in setup.py. In addition, building 4.4.0 on Ubuntu
> 12.04 went through smoothly.
>
> During the installation and test, however, I got the following minor issues:
>
> 1) 'sudo make install' causes this error at the end (only on Mac)
>
> Installed
> /Library/Python/2.7/site-packages/lucene-4.4.0-py2.7-macosx-10.8-x86_64.egg
> Processing dependencies for lucene==4.4.0
> Searching for lucene==4.4.0
> Reading http://pypi.python.org/simple/lucene/
> Couldn't find index page for 'lucene' (maybe misspelled?)
> Scanning index of all packages (this may take a while)
> Reading http://pypi.python.org/simple/
> No local packages or download links found for lucene==4.4.0
> error: Could not find suitable distribution for
> Requirement.parse('lucene==4.4.0')
> make: *** [install] Error 1

We had a similar thread during the 3.6.2 release and it seemed at the time 
that running 'make test' directly after a clean, instead of running 'make', 
then 'make test', could cause this.

Andi..

>
>
> 2) 'make test' permission issue --'sudo make test' runs fine. (both on Mac
> and Ubuntu)
>
> running build_ext
> running install
> running bdist_egg
> running egg_info
> writing lucene.egg-info/PKG-INFO
> error: lucene.egg-info/PKG-INFO: Permission denied
> make: *** [install-test] Error 1
>
>
> Thanks,
> Taka
>
>
> On Sun, Aug 18, 2013 at 3:26 PM, Taka Epsilon <taka.epsilon@gmail.com>wrote:
>
>> Thanks a lot for your help.
>>
>> It turned out that the error was caused by Python installed with
>> Homebrew-- somehow the Homebrew Python was invoking xcrun during the build.
>> So I've uninstalled the Homebrew Python.
>>
>> Now I'm building with the default Python with Mac and looking into the
>> following error:
>>
>> clang -fno-strict-aliasing -fno-common -dynamic -g -Os -pipe -fno-common
>> -fno-strict-aliasing -fwrapv -mno-fused-madd -DENABLE_DTRACE -DMACOSX
>> -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g -Os -Wall
>> -Wstrict-prototypes -DENABLE_DTRACE -arch i386 -arch x86_64 -dynamiclib
>> -D_jcc_lib -DJCC_VER="2.16"
>> -I/Library/Java/JavaVirtualMachines/1.6.0_29-b11-402.jdk/Contents/Home/include
>> -I_jcc -Ijcc/sources
>> -I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7
>> -c jcc/sources/JCCEnv.cpp -o
>> build/temp.macosx-10.8-intel-2.7/jcc/sources/JCCEnv.o -DPYTHON
>> -fno-strict-aliasing -Wno-write-strings
>> clang: warning: argument unused during compilation: '-mno-fused-madd'
>> clang: warning: argument unused during compilation: '-dynamiclib'
>> clang++ -Wl,-x -dynamiclib -undefined dynamic_lookup -arch i386 -arch
>> x86_64 build/temp.macosx-10.8-intel-2.7/jcc/sources/jcc.o
>> build/temp.macosx-10.8-intel-2.7/jcc/sources/JCCEnv.o -o
>> build/lib.macosx-10.8-intel-2.7/libjcc.dylib -framework JavaVM -l
>> -install_name @rpath/libjcc.dylib -current_version 2.16
>> -compatibility_version 2.16
>> clang: error: no such file or directory: '@rpath/libjcc.dylib'
>> error: command 'clang++' failed with exit status 1
>>
>>
>>
>> On Sun, Aug 18, 2013 at 2:12 PM, Andi Vajda <vajda@apache.org> wrote:
>>
>>>
>>> On Aug 18, 2013, at 21:48, Taka Epsilon <taka.epsilon@gmail.com> wrote:
>>>
>>>> I'm new to PyLucene and trying to build JCC 2.17 on Mac OS X 10.8.4 with
>>>> Python 2.7 and Java 1.6. But the 'python setup.py build' command is
>>> failing
>>>> with the following error with the default setup.py. Any idea?
>>>>
>>>>
>>>> xcrun clang -fno-strict-aliasing -fno-common -dynamic
>>> -I/usr/local/include
>>>> -I/usr/local/opt/sqlite/include -isysroot
>>>>
>>> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk
>>>
>>> What is 'xcrun clang' ?
>>>
>>> I suspect that you need to adapt the compiler and linker flags in
>>> setup.py to this compiler and linker combination.
>>>
>>> If you figure it out and send in a patch I'll merge it in. You should add
>>> a new darwin/clang variant in the CFLAGS and LFLAGS dicts in setup.py, or
>>> use gcc instead when compiling Python itself as you seem to have done.
>>>
>>> Andi..
>>>
>>>>
>>> -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/System/Library/Frameworks/Tk.framework/Versions/8.5/Headers
>>>> -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -dynamiclib -D_jcc_lib
>>>> -DJCC_VER="2.17"
>>>>
>>> -I/Library/Java/JavaVirtualMachines/1.6.0_29-b11-402.jdk/Contents/Home/include
>>>>
>>> -I/Library/Java/JavaVirtualMachines/1.6.0_29-b11-402.jdk/Contents/Home/include/darwin
>>>> -I_jcc -Ijcc/sources
>>>>
>>> -I/usr/local/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/include/python2.7
>>>> -c jcc/sources/JCCEnv.cpp -o
>>>> build/temp.macosx-10.8-x86_64-2.7/jcc/sources/JCCEnv.o -DPYTHON
>>>> -fno-strict-aliasing -Wno-write-strings
>>>> clang: warning: argument unused during compilation: '-dynamiclib'
>>>> xcrun -Wl,-x -dynamiclib -undefined dynamic_lookup
>>>> build/temp.macosx-10.8-x86_64-2.7/jcc/sources/jcc.o
>>>> build/temp.macosx-10.8-x86_64-2.7/jcc/sources/JCCEnv.o -o
>>>> build/lib.macosx-10.8-x86_64-2.7/libjcc.dylib
>>>>
>>> -L/Library/Java/JavaVirtualMachines/1.6.0_29-b11-402.jdk/Contents/Home/jre/lib
>>>> -ljava
>>>>
>>> -L/Library/Java/JavaVirtualMachines/1.6.0_29-b11-402.jdk/Contents/Home/jre/lib/server
>>>> -ljvm -Wl,-rpath
>>>>
>>> -Wl,/Library/Java/JavaVirtualMachines/1.6.0_29-b11-402.jdk/Contents/Home/jre/lib
>>>> -Wl,-rpath
>>>>
>>> -Wl,/Library/Java/JavaVirtualMachines/1.6.0_29-b11-402.jdk/Contents/Home/jre/lib/server
>>>> -Wl,-S -install_name @rpath/libjcc.dylib -current_version 2.17
>>>> -compatibility_version 2.17
>>>> xcrun: error: unrecognized option: -Wl,-x
>>>>
>>>>
>>>>
>>>> On Sun, Aug 18, 2013 at 12:28 PM, Thomas Koch <koch@orbiteam.de> wrote:
>>>>
>>>>> I could build JCC 2.17 and PyLucene 4.4.0 und  Mac OS X 10.8.4 (64-bit
>>>>> only -  Python 2.7, Java 1.6). All tests did pass and samples work like
>>>>> expected.
>>>>>
>>>>> +1
>>>>>
>>>>>
>>>>> regards
>>>>> Thomas
>>>>> --
>>>>> Am 17.08.2013 um 16:52 schrieb Andi Vajda <vajda@apache.org>:
>>>>>
>>>>>>
>>>>>> The PyLucene 4.4.0-1 release tracking the recent release of Apache
>>>>> Lucene 4.4.0 is ready.
>>>>>>
>>>>>> A release candidate is available from:
>>>>>> http://people.apache.org/~vajda/staging_area/
>>>>>>
>>>>>> A list of changes in this release can be seen at:
>>>>>
>>> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_4_4/CHANGES
>>>>>>
>>>>>> PyLucene 4.4.0 is built with JCC 2.17 included in these release
>>>>> artifacts:
>>>>>> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>>>>>>
>>>>>> A list of Lucene Java changes can be seen at:
>>>>>
>>> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_4_4_0/lucene/CHANGES.txt
>>>>>>
>>>>>> Please vote to release these artifacts as PyLucene 4.4.0-1.
>>>>>>
>>>>>> Thanks !
>>>>>>
>>>>>> Andi..
>>>>>>
>>>>>> ps: the KEYS file for PyLucene release signing is at:
>>>>>> http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
>>>>>> http://people.apache.org/~vajda/staging_area/KEYS
>>>>>>
>>>>>> pps: here is my +1
>>>>>
>>>>>
>>>
>>
>>
>

Mime
View raw message