[SciPy-user] Building SciPy on OS X: Universal binary issues

Josh Marshall josh.p.marshall at gmail.com
Mon Dec 11 14:46:22 CST 2006


Thanks for that line Robert.

Executing that command line definitely chooses gfortran.

I am now running into this error:

compiling C sources
C compiler: gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/ 
MacOSX10.4u.sdk -fno-strict-aliasing -Wno-long-double -no-cpp-precomp  
-mno-fused-madd -fno-common -dynamic -DNDEBUG -g -O3

creating build/temp.macosx-10.3-fat-2.4/Lib/linsolve
creating build/temp.macosx-10.3-fat-2.4/Lib/linsolve/SuperLU
creating build/temp.macosx-10.3-fat-2.4/Lib/linsolve/SuperLU/SRC
compile options: '-DUSE_VENDOR_BLAS=1 -c'
gcc: Lib/linsolve/SuperLU/SRC/zgscon.c
gcc: cannot specify -o with -c or -S and multiple compilations
gcc: cannot specify -o with -c or -S and multiple compilations
error: Command "gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/ 
MacOSX10.4u.sdk -fno-strict-aliasing -Wno-long-double -no-cpp-precomp  
-mno-fused-madd -fno-common -dynamic -DNDEBUG -g -O3 - 
DUSE_VENDOR_BLAS=1 -c Lib/linsolve/SuperLU/SRC/zgscon.c -o build/ 
temp.macosx-10.3-fat-2.4/Lib/linsolve/SuperLU/SRC/zgscon.o" failed  
with exit status 1

Any ideas on how to resolve this? It goes away if I don't try to  
compile as universal binary.

Regards,
Josh

On 12/12/2006, at 5:00 AM, scipy-user-request at scipy.org wrote:

> Message: 3
> Date: Sun, 10 Dec 2006 17:33:20 -0600
> From: Robert Kern <robert.kern at gmail.com>
> Subject: Re: [SciPy-user] Building SciPy on OS X: Universal binary
> 	issues
> To: SciPy Users List <scipy-user at scipy.org>
> Message-ID: <457C9940.90004 at gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Josh Marshall wrote:
>
>> However, as a related question, if I have both g77 and gfortran
>> installed, how do I select gfortran as the compiler? I have tried
>> various combinations of lines similar to
>>
>> python setup.py config --fcompiler=gnu95 build
>>
>> but g77 is always selected for the build.
>
> As far as I know, "config --fcompiler=gnu95" only sets the compiler  
> for the
> configuration steps (i.e. finding ATLAS and such). I don't think it  
> sets the
> FORTRAN compiler for any of the subsequent steps.
>
> python setup.py config --fcompiler=gnu95 build_src build_clib -- 
> fcompiler=gnu95
> build_ext --fcompiler=gnu95 build
>
> -- 
> 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



More information about the SciPy-user mailing list