> On Nov 11, 2014, at 15:35, Sid Probstein <sidprobst...@gmail.com> wrote:
> 
> Hi, Andi,
> 
> Really appreciate the reply. Do you have any thoughts on how to resolve? I 
> installed gcc-4.2 which is what the Apple python is built with, but that 
> doesn't seem to work either (start getting errors about unsupported file 
> format). It seems like Python for OS/X doesn't install a binary one can use - 
> am I missing something? I'll happily write it up and post it, if I find the 
> solution... thanks again. :-)

I've not upgraded to OS X 10.10 yet so I haven't reproduced the problem yet 
myself.
Building Python from sources takes about 10 minutes. See python.org for 
instructions. It's a good idea to also install setuptools.

Andi..

> 
> Cheers,
> --Sid
> 
>> On Tue, Nov 11, 2014 at 6:06 PM, Sid Probstein <sidprobst...@gmail.com> 
>> wrote:
>> Thanks very much! Doh. :-)
>> 
>>> On Tue, Nov 11, 2014 at 5:59 PM, Andi Vajda <va...@apache.org> wrote:
>>> 
>>> On Tue, 11 Nov 2014, Sid Probstein wrote:
>>> 
>>>> Hi,
>>>> 
>>>> I'm trying to build JCC on OS/X 10.10. I've downloaded
>>>> pylucene-4.10.1.1-src. When I run jcc's setup.py build, the following error
>>>> occurs:
>>>> 
>>>> ld: internal error: atom not found in
>>>> symbolIndex(__ZN7JNIEnv_13CallIntMethodEP8_jobjectP10_jmethodIDz) for
>>>> architecture x86_64
>>>> 
>>>> Note that I did modify jcc's setup.py to add '-framework', 'Python' under
>>>> LFLAGS:
>>>> 
>>>> 'darwin/frameworks': ['-framework', 'JavaVM'
>>>>                                   '-framework', 'Python'],
>>>> 
>>>> Any suggestions or pointers most appreciated. The relevant build errors are
>>>> below... Thanks! :-)
>>> 
>>> You must ensure that the compiler used to build Python is the same as the 
>>> compiler you're using. If you did not build Python then it's likely you're 
>>> htting a clang/gcc mismatch and you need to rebuild Python from sources, 
>>> using the same compiler as you're using to build JCC.
>>> 
>>> Andi..
>>> 
>>> 
>>>> 
>>>> ----- >8
>>>> 
>>>> building 'jcc' extension
>>>> creating build/temp.macosx-10.6-x86_64-2.7
>>>> creating build/temp.macosx-10.6-x86_64-2.7/jcc
>>>> creating build/temp.macosx-10.6-x86_64-2.7/jcc/sources
>>>> clang -fno-strict-aliasing -fno-common -dynamic -arch i386 -arch x86_64 -g
>>>> -O2 -DNDEBUG -g -O3 -dynamiclib -D_jcc_lib -DJCC_VER="2.21"
>>>> -I/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/include
>>>> -I/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/include/darwin
>>>> -I_jcc -Ijcc/sources
>>>> -I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c
>>>> jcc/sources/jcc.cpp -o build/temp.macosx-10.6-x86_64-2.7/jcc/sources/jcc.o
>>>> -DPYTHON -fno-strict-aliasing -Wno-write-strings
>>>> clang: warning: argument unused during compilation: '-dynamiclib'
>>>> clang -fno-strict-aliasing -fno-common -dynamic -arch i386 -arch x86_64 -g
>>>> -O2 -DNDEBUG -g -O3 -dynamiclib -D_jcc_lib -DJCC_VER="2.21"
>>>> -I/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/include
>>>> -I/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/include/darwin
>>>> -I_jcc -Ijcc/sources
>>>> -I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c
>>>> jcc/sources/JCCEnv.cpp -o
>>>> build/temp.macosx-10.6-x86_64-2.7/jcc/sources/JCCEnv.o -DPYTHON
>>>> -fno-strict-aliasing -Wno-write-strings
>>>> clang: warning: argument unused during compilation: '-dynamiclib'
>>>> c++ -Wl,-x -dynamiclib -undefined dynamic_lookup
>>>> build/temp.macosx-10.6-x86_64-2.7/jcc/sources/jcc.o
>>>> build/temp.macosx-10.6-x86_64-2.7/jcc/sources/JCCEnv.o -o
>>>> build/lib.macosx-10.6-x86_64-2.7/libjcc.dylib
>>>> -L/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre/lib
>>>> -ljava
>>>> -L/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre/lib/server
>>>> -ljvm -Wl,-rpath
>>>> -Wl,/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre/lib
>>>> -Wl,-rpath
>>>> -Wl,/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre/lib/server
>>>> -Wl,-S -install_name @rpath/libjcc.dylib -current_version 2.21
>>>> -compatibility_version 2.21
>>>> ld: internal error: atom not found in
>>>> symbolIndex(__ZN7JNIEnv_13CallIntMethodEP8_jobjectP10_jmethodIDz) for
>>>> architecture x86_64
>>>> clang: error: linker command failed with exit code 1 (use -v to see
>>>> invocation)
>>>> error: command 'c++' failed with exit status 1
> 

Reply via email to