Closed GoogleCodeExporter closed 9 years ago
With NumPy downgraded to 1.6.2 there is still a compile error. The error
message is below. Sorry for the ticket title confusion...
HDF5_DIR environment variable not set, checking some standard locations ..
checking /Users/laura ...
checking /usr/local ...
checking /sw ...
checking /opt ...
checking /opt/local ...
HDF5 found in /opt/local
NETCDF4_DIR environment variable not set, checking standard locations..
checking /Users/laura ...
checking /usr/local ...
checking /sw ...
checking /opt ...
checking /opt/local ...
netCDF4 found in /opt/local
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
build_src
building py_modules sources
building extension "netCDF4" sources
build_src: building npy-pkg config files
running build_py
creating build
creating build/lib.macosx-10.3-fat-2.7
copying netcdftime.py -> build/lib.macosx-10.3-fat-2.7
copying netCDF4_utils.py -> build/lib.macosx-10.3-fat-2.7
copying checkversion.py -> build/lib.macosx-10.3-fat-2.7
running build_ext
customize UnixCCompiler
customize UnixCCompiler using build_ext
building 'netCDF4' extension
compiling C sources
C compiler: /usr/bin/gcc-4.2 -fno-strict-aliasing -fno-common -dynamic -arch
ppc -arch i386 -g -O2 -DNDEBUG -g -O3
creating build/temp.macosx-10.3-fat-2.7
compile options: '-I/opt/local/include -I/opt/local/include
-I/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/
numpy/core/include
-I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c'
gcc-4.2: netCDF4.c
/usr/libexec/gcc/powerpc-apple-darwin10/4.2.1/as: assembler
(/usr/bin/../libexec/gcc/darwin/ppc/as or
/usr/bin/../local/libexec/gcc/darwin/ppc/as) for architecture ppc not installed
Installed assemblers are:
/usr/bin/../libexec/gcc/darwin/x86_64/as for architecture x86_64
/usr/bin/../libexec/gcc/darwin/i386/as for architecture i386
In file included from /usr/include/architecture/i386/math.h:626,
from /usr/include/math.h:28,
from /Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/pyport.h:312,
from /Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/Python.h:58,
from netCDF4.c:4:
/usr/include/AvailabilityMacros.h:108:14: warning: #warning Building for Intel
with Mac OS X Deployment Target < 10.4 is invalid.
lipo: can't open input file:
/var/folders/Xx/Xxq0XtVvGCCNmapIJp-5i++++TI/-Tmp-//ccz0J256.out (No such file
or directory)
/usr/libexec/gcc/powerpc-apple-darwin10/4.2.1/as: assembler
(/usr/bin/../libexec/gcc/darwin/ppc/as or
/usr/bin/../local/libexec/gcc/darwin/ppc/as) for architecture ppc not installed
Installed assemblers are:
/usr/bin/../libexec/gcc/darwin/x86_64/as for architecture x86_64
/usr/bin/../libexec/gcc/darwin/i386/as for architecture i386
In file included from /usr/include/architecture/i386/math.h:626,
from /usr/include/math.h:28,
from /Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/pyport.h:312,
from /Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/Python.h:58,
from netCDF4.c:4:
/usr/include/AvailabilityMacros.h:108:14: warning: #warning Building for Intel
with Mac OS X Deployment Target < 10.4 is invalid.
lipo: can't open input file:
/var/folders/Xx/Xxq0XtVvGCCNmapIJp-5i++++TI/-Tmp-//ccz0J256.out (No such file
or directory)
error: Command "/usr/bin/gcc-4.2 -fno-strict-aliasing -fno-common -dynamic
-arch ppc -arch i386 -g -O2 -DNDEBUG -g -O3 -I/opt/local/include
-I/opt/local/include
-I/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/
numpy/core/include
-I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c
netCDF4.c -o build/temp.macosx-10.3-fat-2.7/netCDF4.o" failed with exit status 1
Original comment by benkoz...@gmail.com
on 25 Feb 2013 at 9:28
We think the problem was related to 32/64-bit architectures on Mac OS and seem
to have resolved the problem...
Original comment by benkoz...@gmail.com
on 28 Feb 2013 at 11:15
Original comment by whitaker.jeffrey@gmail.com
on 7 Mar 2013 at 11:31
Original issue reported on code.google.com by
benkoz...@gmail.com
on 25 Feb 2013 at 7:13