[netCDF #IOZ-697451]: configure error in mac leopard for netcdf 4

Hi,

> Hello,
> I am trying to compile 32bit NETCDF 4 in MAC OS X server 10.5.7 2 x 3 GHz
> quad core Intel xeon processor with 2 GB ram. The following are the env
> settings.
> 
> export F77=ifort
> 
> export F90=ifort
> 
> export CC=/usr/bin/cc
> 
> export CXX=/usr/bin/c++
> 
> export FFLAGS='-i4 -xP -O3 -ip -no-prec-div'
> 
> export F90FLAGS='-i4 -xP -O3 -ip -no-prec-div'
> 
> export CFLAGS='-O3 -xP -fno-common -DMACOS'
> 
> export CXXFLAGS='-O3 -xP -fno-common -DMACOS'
> 
> ./configure --prefix=/usr/local/m32/netcdf
> 
> 
> Configure fails with the following

It usually works better to use the Intel C compiler icc with the Intel
Fortran compiler ifort.  For example, we have found the following settings 
work:

CC=icc 
CFLAGS=-O3 -xN -ip -no-prec-div -static 
CXX=icpc 
CXXFLAGS=-O3 -xN -ip -no-prec-div -static
FC=ifort 
FCFLAGS=-O3 -xN -ip -no-prec-div -static 
F77=ifort 
FFLAGS=-O3 -xN -ip -no-prec-div -static

Remember to invoke

  make distclean

first, before rerunning the configure script.

We don't have ifort installed on our MacOS test platform currently,
so cannot easily test these settings on MacOS X.

--Russ

> checking build system type... i386-apple-darwin9.7.0
> 
> checking host system type... i386-apple-darwin9.7.0
> 
> checking for a BSD-compatible install... /usr/bin/install -c
> 
> checking whether build environment is sane... yes
> 
> checking for a thread-safe mkdir -p... ./install-sh -c -d
> 
> checking for gawk... no
> 
> checking for mawk... no
> 
> checking for nawk... no
> 
> checking for awk... awk
> 
> checking whether make sets $(MAKE)... yes
> 
> configure: checking user options
> 
> checking whether CXX is set to ''... no
> 
> checking whether FC is set to ''... no
> 
> checking whether F90 is set to ''... no
> 
> checking whether a NCIO_MINBLOCKSIZE was specified... 256
> 
> checking whether this is a netCDF-4.x build... yes
> 
> checking whether extra valgrind tests should be run... no
> 
> configure: Processing NetCDF-4 options.
> 
> checking whether netCDF-4 is to be built... no
> 
> checking whether new netCDF-4 C++ API is to be built... no
> 
> checking whether HDF5 should do data conversions... no
> 
> checking whether extra example tests should be run... no
> 
> checking whether parallel IO tests should be run... no
> 
> checking whether a location for the HDF5 library was specified...
> 
> checking whether a location for the ZLIB library was specified...
> 
> checking whether a location for the SZLIB library was specified...
> 
> checking whether a default cache size for HDF5 was specified... 32000000
> 
> checking whether a default cache maximum number of elements for HDF5 was
> specified... 1000
> 
> checking whether a default cache preemption for HDF5 was specified... 0.75
> 
> checking whether netCDF-4 logging is enabled... no
> 
> checking whether DAP client is to be built... no
> 
> checking whether dap remote testing should be enabled... no
> 
> checking whether netCDF extra tests should be run (developers only)... no
> 
> checking whether documentation is to be installed... no
> 
> checking whether Fortran compiler(s) should be tested during configure...
> yes
> 
> checking whether FFIO will be used... no
> 
> checking whether to skip C++, F77, or F90 APIs if compiler is broken... yes
> 
> checking whether only the C library is desired... no
> 
> checking whether examples should be built... yes
> 
> checking whether F77 API is desired... yes
> 
> checking whether F90 API is desired... yes
> 
> checking whether fortran type sizes should be checked... yes
> 
> checking whether C API is desired... yes
> 
> checking where to get netCDF C-only library for separate fortran
> libraries...
> 
> checking whether CXX API is desired... yes
> 
> checking whether v2 netCDF API should be built... yes
> 
> checking whether the ncgen/ncdump should be built... yes
> 
> checking whether large file (> 2GB) tests should be run... no
> 
> checking whether benchmaks should be run (experimental)... no
> 
> checking whether extreme numbers should be used in tests... yes
> 
> checking where to put large temp files if large file tests are run... .
> 
> checking whether a win32 DLL is desired... no
> 
> checking whether separate fortran libs are desired... no
> 
> configure: finding C compiler
> 
> checking for C compiler default output file name...
> 
> configure: error: C compiler cannot create executables
> 
> See `config.log' for more details.
> 
> 
> I am attaching config.log for guidance
> 
> 
> *Note: I have successfully built netcdf in 64 bit*
> 
> --
> With regards
> 
> Dr.R.Jagannathan
> Professor and Head
> Agro Climate Research Centre,
> Tamil Nadu Agricultural University,
> Coimbatore - 641 003 India
> 
> PHONE: Off: 91-422-6611519 Res: 91-422-2453600
> Fax: 91-422-2430657 Mob: 91-94438 89891
> 
> 

Russ Rew                                         UCAR Unidata Program
address@hidden                     http://www.unidata.ucar.edu



Ticket Details
===================
Ticket ID: IOZ-697451
Department: Support netCDF
Priority: Normal
Status: Closed