Charles R Harris wrote:
> 
> 
>      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 -I/Library/
>      Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/
>      numpy/core/include -c scipy/optimize/Zeros/bisect.c -o build/
>      temp.macosx-10.3-ppc-2.5/scipy/optimize/Zeros/bisect.o" failed with
>      exit status 1
> 
>      I will try removing -Wno-long-double from the appropriate places and
>      muddle through the build (I should note that I'm on a PPC machine
>      which may be one of the boundary cases where all of this long double
>      confusion is coming from.)
> 
> 
>  I suspect David (C) can fix this one. PPC has it's own, non-ieee,
>  version of long doubles and so is a bit of an outlier.

The work on long double has not touched build options. For all I can
remember, the -wno-long-double flag was there for quite some time. Maybe
a python distutils bug ? I have a ppc minimac at home, I may fire it up
to check this, but I don't think it is a regression by numpy,

David
_______________________________________________
Scipy-dev mailing list
Scipy-dev@[...].org
http://mail.scipy.org/mailman/listinfo/scipy-dev