[SciPy-user] numpy 64 bit build on mac os x

David Cournapeau david@ar.media.kyoto-u.ac...
Sat May 16 02:21:02 CDT 2009

Roger Herikstad wrote:
> Hi,
>  Thanks for your quick reply. Adding those CFLAGS revealed another
> problem, though. I now get the following error:
>  building 'numpy.core._sort' extension
> 1571 compiling C sources
> 1572 C compiler: gcc -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes
> -O3 -Wall -DNDEBUG -g -fwrapv -Wstrict-prototypes -arch ppc -arch
> x86_64 -arch ppc64 -arch i386      -I/usr/local/include
> 1573
> 1574 compile options: '-Inumpy/core/include
> -Ibuild/src.macosx-10.5-universal-2.6/numpy/core/include/numpy
> -Inumpy/core/src -Inumpy/core/src/multiarray -Inumpy/core/s
> rc/umath -Inumpy/core/include
> -I/Library/Frameworks/Python64.framework/Versions/2.6/include/python2.6
> -Ibuild/src.macosx-10.5-universal-2.6/numpy/core/src/multia     rray
> -Ibuild/src.macosx-10.5-universal-2.6/numpy/core/src/umath -c'
> 1575 gcc: build/src.macosx-10.5-universal-2.6/numpy/core/src/_sortmodule.c
> 1576 In file included from numpy/core/include/numpy/ndarrayobject.h:33,
> 1577                  from numpy/core/include/numpy/noprefix.h:7,
> 1578                  from numpy/core/src/_sortmodule.c.src:29:
> 1579 numpy/core/include/numpy/npy_endian.h:33:10: error: #error
> Unknown CPU: can not set endianness
> Is this an issue of the mixed endianness between ppc and intel macs?

Each -arch should imply a new read of the header (AFAIK, -arch is just a
convenience to run the target specific compiler corresponding to each
architecture), so this is strange. I will look into it,


More information about the SciPy-user mailing list