> Hi all, > > I'm running into difficulties with netcdf-4.1.1, built with the latest > (11.1, release 069) of the Intel compilers on a 64bit CentOS platform. > > When linking against libnetcdf.a, either with WRF3.2 or via "make check" > after installing netcdf, I get a bunch of undefined references to > various nf_ subroutines. > > I don't run into these problems with 4.0.1. > > I've configured netcdf as follows: > > configure --prefix=/ash1/ktyle --enable-netcdf-4 --disable-cxx > --enable-benchmarks --enable-ncgen4 --with-hdf5=/ash1/ktyle > --with-szlib=/ash1/ktyle > > with the following env. variables set: > FC=/opt/intel/Compiler/11.1/latest/bin/intel64/ifort > F77=/opt/intel/Compiler/11.1/latest/bin/intel64/ifort > F90=/opt/intel/Compiler/11.1/latest/bin/intel64/ifort > CC=/opt/intel/Compiler/11.1/latest/bin/intel64/icc > CXX=/opt/intel/Compiler/11.1/latest/bin/intel64/icpc > > HDF5 and szip have already been built, no probs there. > > I've attached output from make and make check. > > Thanks in advance, > > Kevin > Howdy Kevin! The netcdf configure script is getting confused, because it expects FC to be ifort, and the path to ifort to be part of the path. To specify the FC as /path/compiler, you need to tell the netcdf build what type of fortran compiler you have, by setting CPPFLAGS to -DpgiFortran. Please let me know if this doesn't help. Thanks, Ed Ticket Details =================== Ticket ID: IXO-940473 Department: Support netCDF Priority: Normal Status: Closed
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.