Greetings Craig!
The issue has to do with a test related to libsz - a fix has recently be added,
but is only avaliable in the nightly build at this point. Please try using the
nightly build to see if this fixes the issue:
ftp.unidata.ucar.edu/pub/netcdf/snapshot/netcdf-4-daily.tar.gz
Cheers!
Sean
> Hi,
>
> I am trying to build NetCDF 4.1.3 on Mac OS X 10.7 (Lion) with the Intel
> 12.0.4.184 compilers using these settings:
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> setenv USR_LOCAL /usr/local
> setenv LIBZ /usr
> setenv HDF5 ${USR_LOCAL}/phdf5
>
> setenv INCS "-I${HDF5}/include"
> setenv LIBS "-L${HDF5}/lib -lhdf5 -L${LIBZ}/lib -lz"
>
> setenv NETCDF4 ${USR_LOCAL}/netcdf4
>
> setenv CPP "cpp -C -P -xassembler-with-cpp -traditional"
> setenv CC mpicc
> setenv CXX mpicxx
> setenv F77 mpif77
> setenv FF mpif77
> setenv FC mpif90
>
> setenv CPPFLAGS "-DNDEBUG -DpgiFortran"
> setenv CFLAGS "-w -O3 -xHost -ip -fp-model fast=2 -no-prec-div -no-prec-sqrt
> -ftz -no-multibyte-chars -m64 ${INCS}"
> setenv CXXFLAGS "-w -O3 -xHost -ip -fp-model fast=2 -no-prec-div
> -no-prec-sqrt -ftz -no-multibyte-chars -m64 ${INCS}"
> setenv FCLAGS "-w -O3 -xHost -ip -fp-model fast=2 -no-heap-arrays
> -no-prec-div -no-prec-sqrt -ftz -align all -m64 ${INCS}"
> setenv FFLAGS "-w -O3 -xHost -ip -fp-model fast=2 -no-heap-arrays
> -no-prec-div -no-prec-sqrt -ftz -align all -m64 ${INCS}"
> setenv LDFLAGS "-w -O3 -xHost -ip -fp-model fast=2 -no-heap-arrays
> -no-prec-div -no-prec-sqrt -ftz -m64 ${LIBS}"
>
> ./configure --prefix=${NETCDF4} --enable-parallel --with-zlib=/usr/lib
> --enable-large-file-tests --enable-benchmarks
>
> make |& tee make.log
> make check |& tee check.log
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
> It builds fine and all the tests are successful, until it hits this compiler
> glitch:
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> libtool: link: mpif90 -I../fortran -I../f90 -I../f90 -I../include -I../oc -g
> -w -O3 -xHost -ip -fp-model fast=2 -no-heap-arrays -no-prec-div -no-prec-sqrt
> -ftz -m64 -o f90tst_vars4 f90tst_vars4.o -L/usr/local/phdf5/lib
> -L/usr/local/szip/lib -L/usr/lib ../fortran/.libs/libnetcdff.a
> /Users/cmattock/Downloads/netcdf-4.1.3/liblib/.libs/libnetcdf.a
> /usr/local/phdf5/lib/libhdf5_hl.dylib -lcurl
> /usr/local/phdf5/lib/libhdf5.dylib /usr/local/szip/lib/libsz.dylib -lm -lz
> mpif90 -I../fortran -I../f90 -I../f90 -I../include -I../oc -g -c -o
> f90tst_vars2.o f90tst_vars2.f90
> f90tst_vars2.f90(37): error #6418: This name has already been assigned a data
> type. [CACHE_SIZE]
> integer, parameter :: CACHE_SIZE = 8, CACHE_NELEMS = 571, CACHE_PREEMPTION =
> 66
> ------------------------^
> f90tst_vars2.f90(37): error #6418: This name has already been assigned a data
> type. [CACHE_NELEMS]
> integer, parameter :: CACHE_SIZE = 8, CACHE_NELEMS = 571, CACHE_PREEMPTION =
> 66
> ----------------------------------------^
> f90tst_vars2.f90(77): error #6284: There is no matching specific function for
> this generic function reference. [NF90_DEF_VAR]
> call check(nf90_def_var(ncid, VAR5_NAME, NF90_INT, dimids, varid5, chunksizes
> = chunksizes, &
> -------------^
> f90tst_vars2.f90(85): error #6404: This name does not have a type, and must
> have an explicit type. [NF90_SET_VAR_CHUNK_CACHE]
> call check(nf90_set_var_chunk_cache(ncid, varid1, CACHE_SIZE, &
> -------------^
> compilation aborted for f90tst_vars2.f90 (code 1)
> gnumake[2]: *** [f90tst_vars2.o] Error 1
> gnumake[1]: *** [check-am] Error 2
> make: *** [check-recursive] Error 1
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
> Is this repetitive parameter information coming in through the "use netcdf"
> import? What is the best way to fix this?
>
> Thank you!
> Craig
>
>
Ticket Details
===================
Ticket ID: XCV-291469
Department: Support netCDF
Priority: Normal
Status: Open
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.