[SciPy-user] Scipy-0.6.0 fails to build on MacOS 10.4.10 with gfortran (gcc4.2.2)

Robert Kern robert.kern@gmail....
Thu Nov 15 02:09:27 CST 2007


David Cournapeau wrote:
> Robert Kern wrote:
>> Sebastien Maret wrote:
>>> Hello,
>>>
>>> The error log is below:
>>>
>>> /sw/bin/gfortran -Wall -L/sw/lib build/temp.macosx-10.4-i386-2.5/build/src.macosx-10.4-i386-2.5/scipy/fftpack/_fftpackmodule.o build/temp.macosx-10.4-i386-2.5/scipy/fftpack/src/zfft.o build/temp.macosx-10.4-i386-2.5/scipy/fftpack/src/drfft.o build/temp.macosx-10.4-i386-2.5/scipy/fftpack/src/zrfft.o build/temp.macosx-10.4-i386-2.5/scipy/fftpack/src/zfftnd.o build/temp.macosx-10.4-i386-2.5/build/src.macosx-10.4-i386-2.5/fortranobject.o /sw/lib/djbfft.a -L/sw/lib -L/sw/lib/gcc4.2/lib/gcc/i686-apple-darwin8/4.2.2 -Lbuild/temp.macosx-10.4-i386-2.5 -ldfftpack -lfftw3 -lgfortran -o build/lib.macosx-10.4-i386-2.5/scipy/fftpack/_fftpack.so
>> Don't use the LDFLAGS environment variable. This overwrites the link options,
>> including the ones which provide the libpython2.5 library.
> I was wondering, since this is causing so much trouble, wouldn't it be 
> easier to just emit a warning when LDFLAGS or CFLAGS is used, and 
> disable it ?

Not alone, no. It's the only way to override those settings. Particularly in the
case of Fortran compilers, which will often be quite different from the C
compiler used to build Python itself, this is an important feature. If you make
another way to fully override those settings, then you may change the LDFLAGS
behavior.

-- 
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