[SciPy-User] Problems building SciPy on OS X due to ppc64 issues

[Robert Kern]

On Fri, Oct 8, 2010 at 13:14, Dr. David Kirkby <david.kirkby at onetel.net> wrote:
> Numpy and SciPy are used in the Sage project. A ticket has been opened to update
> Numpy to 1.5.0 and SciPy to 0.8.
>
> We hit a problem with Numpy and Solaris, though the number developers have now
> committed a fix for that issue.
>
> However, we have an issue with people being unable to build on OS X. I
> personally do not have an OS X machine, but there's a log of a failed build here:
>
> http://sage.math.washington.edu/home/palmieri/misc/scipy-0.8.log
>
> For reasons I think are rather stupid, we use a script sage_fortran which is the
> Fortran compiler, so references below to
> /Applications/sage_builds/numpy/sage-4.6.alpha2/local/bin/sage_fortran
>
> is actually just a link to 'gfortran'
>
> It seems to resolve around the error message about two files "...have the same
> architectures (ppc64) and can't be in the same fat output file
>
> See below.
>
> creating build/temp.macosx-10.6-i386-2.6/scipy/fftpack
> creating build/temp.macosx-10.6-i386-2.6/scipy/fftpack/src
> creating build/temp.macosx-10.6-i386-2.6/scipy/fftpack/src/dfftpack
> compile options:
> '-I/Applications/sage_builds/numpy/sage-4.6.alpha2/local/lib/python2.6/site-packages/numpy/core/include
> -c'
> sage_fortran:f77: scipy/fftpack/src/dfftpack/dcosqb.f
> lipo: /var/folders/JV/JVYCpshdHd4FFoThuUgD8k+++TI/-Tmp-//ccHZoMkv.out and
> /var/folders/JV/JVYCpshdHd4FFoThuUgD8k+++TI/-Tmp-//ccpHWmlC.out have the same
> architectures (ppc64) and can't be in the same fat output file
> lipo: /var/folders/JV/JVYCpshdHd4FFoThuUgD8k+++TI/-Tmp-//ccHZoMkv.out and
> /var/folders/JV/JVYCpshdHd4FFoThuUgD8k+++TI/-Tmp-//ccpHWmlC.out have the same
> architectures (ppc64) and can't be in the same fat output file
> error: Command
> "/Applications/sage_builds/numpy/sage-4.6.alpha2/local/bin/sage_fortran -Wall
> -ffixed-form -fno-second-underscore -arch ppc -arch x86_64 -arch ppc64 -fPIC -O3
> -funroll-loops
> -I/Applications/sage_builds/numpy/sage-4.6.alpha2/local/lib/python2.6/site-packages/numpy/core/include
> -c -c scipy/fftpack/src/dfftpack/dcosqb.f -o

Are the multiple "-c" options causing issues? From the build log, it
looks like "-c" is being added explicitly somewhere.

compile options:
'-I/Applications/sage_builds/numpy/sage-4.6.alpha2/local/lib/python2.6/site-packages/numpy/core/include
-c'

Exactly where did the gfortran compiler come from? What version is it?
What architecture is the machine doing the 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