[SciPy-user] scipy 0.6 installation problem on os x 10.5.5

[Ritchie Cai]

Thanks, I just got it to work. Actually I tried 4.0 before, but I was  
just doing a simple easy_install scipy, and it gives some other error  
messages. I guess I should have compiled from source like this:

export MACOSX_DEPLOYMENT_TARGET=10.5
     cd ../scipy
     python setup.py build_src build_clib --fcompiler=gnu95 build_ext  
--fcompiler=gnu95 build
     sudo python setup.py install

On Oct 26, 2008, at 12:45 PM, Robert Kern wrote:

> On Sun, Oct 26, 2008 at 11:50, Ritchie <voodoochild2006 at gmail.com>  
> wrote:
>> I'm trying to install scipy 0.6 on my leopard MBP, after a
>> python setup.py build
>> as root, I got the following error message :
>> compiler: gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp
>> -mno-fused-madd -fno-common -dynamic -DNDEBUG -g -Os -Wall
>> -Wstrict-prototypes -DMACOSX -I/usr/include/ffi -DENABLE_DTRACE - 
>> arch i386
>> -arch ppc -pipe
>> creating build/temp.macosx-10.5-i386-2.5/scipy/optimize/Zeros
>> compile options: '-c'
>> gcc: scipy/optimize/Zeros/brenth.c
>> cc1: error: unrecognized command line option "-Wno-long-double"
>> cc1: error: unrecognized command line option "-Wno-long-double"
>> lipo: can't open input file: /var/tmp//ccaG7ngI.out (No such file or
>> directory)
>> cc1: error: unrecognized command line option "-Wno-long-double"
>> cc1: error: unrecognized command line option "-Wno-long-double"
>> lipo: can't open input file: /var/tmp//ccaG7ngI.out (No such file or
>> directory)
>> error: Command "gcc -fno-strict-aliasing -Wno-long-double -no-cpp- 
>> precomp
>> -mno-fused-madd -fno-common -dynamic -DNDEBUG -g -Os -Wall
>> -Wstrict-prototypes -DMACOSX -I/usr/include/ffi -DENABLE_DTRACE - 
>> arch i386
>> -arch ppc -pipe -c scipy/optimize/Zeros/brenth.c -o
>> build/temp.macosx-10.5-i386-2.5/scipy/optimize/Zeros/brenth.o"  
>> failed with
>> exit status 1
>>
>> I googled for a while, could not find any solution. Anybody has any  
>> idea?
>> I'm using xcode 3.1.1, gcc-4.2.1, gfortran-4.2.3.
>
> That's your problem. You should use the same version of gcc (4.0.1)
> that compiled your Python executable. It looks like gcc dropped a flag
> in the intervening period, but Python tries to use the same flags it
> was built with to build extensions. I haven't had any problem mixing
> gcc 4.0.1 with gfortran 4.2.x. At least for building scipy.
>
> -- 
> Robert Kern
>
> "I have come to believe that the whole world is an enigma, a harmless
> enigma that is made terrible by our own mad attempt to interpret it as
> though it had an underlying truth."
>  -- Umberto Eco
> _______________________________________________
> SciPy-user mailing list
> SciPy-user at scipy.org
> http://projects.scipy.org/mailman/listinfo/scipy-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.scipy.org/pipermail/scipy-user/attachments/20081026/4cae99a7/attachment.html>