[Numpy-discussion] Problems installing on OS X

Christopher Hanley chanley@stsci....
Sat Jan 19 20:58:42 CST 2008


Greetings,

I am by no means an installation expert.  However, looking over your 
build log it looks like the Python you are using is the one that came 
with Mac OS X.  My experience has been that it is necessary to install 
the Mac OS X Python version available at 
http://www.python.org/download/.  The one that comes installed with OS X 
seems to be a custom job by Apple.

However, I am sure that the true installation experts on the list will 
have better information or advice for you.

Chris


-- 
Christopher Hanley
Systems Software Engineer
Space Telescope Science Institute
3700 San Martin Drive
Baltimore MD, 21218
(410) 338-4338





Sam Watson wrote:
> Dear all,
>
> I am running OS X 10.4.11, and when I run gcc -v, I get:
>
> Using built-in specs.
> Target: powerpc-apple-darwin8
> Configured with: /private/var/tmp/gcc/gcc-5026.obj~19/src/configure -- 
> disable-checking --prefix=/usr --mandir=/share/man --enable- 
> languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^+.-]*$/ 
> s/$/-4.0/ --with-gxx-include-dir=/include/gcc/darwin/4.0/c++ -- 
> build=powerpc-apple-darwin8 --host=powerpc-apple-darwin8 -- 
> target=powerpc-apple-darwin8
> Thread model: posix
> gcc version 4.0.0 (Apple Computer, Inc. build 5026)
>
> However, when I move into the numpy-1.0.4 directory and run python  
> setup.py install, I get hundreds of error messages which appear to  
> relate to my C compiler.  Here is the output with lots of similar C  
> messages in the middle omitted:
>
> non-existing path in 'numpy/distutils': 'site.cfg'
> F2PY Version 2_4422
> blas_opt_info:
>    FOUND:
>      extra_link_args = ['-Wl,-framework', '-Wl,Accelerate']
>      define_macros = [('NO_ATLAS_INFO', 3)]
>      extra_compile_args = ['-faltivec', '-I/System/Library/Frameworks/ 
> vecLib.framework/Headers']
>
> lapack_opt_info:
>    FOUND:
>      extra_link_args = ['-Wl,-framework', '-Wl,Accelerate']
>      define_macros = [('NO_ATLAS_INFO', 3)]
>      extra_compile_args = ['-faltivec']
>
> running install
> running build
> running config_cc
> unifing config_cc, config, build_clib, build_ext, build commands -- 
> compiler options
> running config_fc
> unifing config_fc, config, build_clib, build_ext, build commands -- 
> fcompiler options
> running build_src
> building py_modules sources
> building extension "numpy.core.multiarray" sources
> Generating build/src.macosx-10.3-fat-2.5/numpy/core/config.h
> customize NAGFCompiler
> Could not locate executable f95
> customize AbsoftFCompiler
> Could not locate executable f90
> Found executable /sw/bin/f77
> absoft: no Fortran 90 compiler found
> absoft: no Fortran 90 compiler found
> absoft: no Fortran 90 compiler found
> absoft: no Fortran 90 compiler found
> absoft: no Fortran 90 compiler found
> absoft: no Fortran 90 compiler found
> customize IBMFCompiler
> Could not locate executable xlf90
> Could not locate executable xlf
> customize IntelFCompiler
> Could not locate executable ifort
> Could not locate executable ifc
> customize GnuFCompiler
> Found executable /sw/bin/g77
> gnu: no Fortran 90 compiler found
> gnu: no Fortran 90 compiler found
> customize GnuFCompiler
> gnu: no Fortran 90 compiler found
> gnu: no Fortran 90 compiler found
> customize GnuFCompiler using config
> 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
>
> compile options: '-I/Library/Frameworks/Python.framework/Versions/2.5/ 
> include/python2.5 -Inumpy/core/src -Inumpy/core/include -I/Library/ 
> Frameworks/Python.framework/Versions/2.5/include/python2.5 -c'
> gcc: _configtest.c
> In file included from _configtest.c:2:
> /Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/ 
> Python.h:18:20: error: limits.h: No such file or directory
> /Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/ 
> Python.h:21:2: error: #error "Something's broken.  UCHAR_MAX should  
> be defined in limits.h."
> /Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/ 
> Python.h:25:2: error: #error "Python's source code assumes C's  
> unsigned char is an 8-bit type."
> /Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/ 
> Python.h:32:19: error: stdio.h: No such file or directory
> /Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/ 
> Python.h:34:5: error: #error "Python.h requires that stdio.h define  
> NULL."
> /Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/ 
> Python.h:37:20: error: string.h: No such file or directory
> /Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/ 
> Python.h:39:19: error: errno.h: No such file or directory
> /Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/ 
> Python.h:41:20: error: stdlib.h: No such file or directory
> ...
>
> /Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/ 
> pystrtod.h:11: error: parse error before 'size_t'
> In file included from _configtest.c:2:
> /Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/ 
> Python.h:134: error: parse error before '*' token
> /Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/ 
> Python.h:134: error: parse error before '*' token
> /Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/ 
> Python.h:134: warning: data definition has no type or storage class
> _configtest.c: In function 'main':
> _configtest.c:9: error: 'FILE' undeclared (first use in this function)
> _configtest.c:9: error: (Each undeclared identifier is reported only  
> once
> _configtest.c:9: error: for each function it appears in.)
> _configtest.c:9: error: 'fp' undeclared (first use in this function)
> _configtest.c:17: warning: incompatible implicit declaration of built- 
> in function 'fprintf'
> lipo: can't figure out the architecture type of: /var/tmp//ccPjVTJJ.out
> failure.
> removing: _configtest.c _configtest.o
>
>
>
>
> I know that my C compiler works, because I do my research in C on a  
> regular basis.  Does anybody have any ideas?
>
> Thanks,
> Sam Watson
> _______________________________________________
> Numpy-discussion mailing list
> Numpy-discussion@scipy.org
> http://projects.scipy.org/mailman/listinfo/numpy-discussion
>   




More information about the Numpy-discussion mailing list