This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Orenthal, > To: <address@hidden> > From: "Orenthal J. Tucker" <address@hidden> > Subject: netcdf problems > Organization: UCAR/Unidata > Keywords: 200107092042.f69Kgq114066 The above message contained the following: > A. Linux glmr-023-20.hsc.edu 2.2.14-5.9 #1 Tue Mar 7 21:07:39 EST 2000 > i686 unknown > > B. 3.5.0 > > C. /proj/pgi/linux86/bin/pgf90 > /usr/bin/gcc > > > D. > > creating cache ./config.cache > checking for top-level source-directory > /proj/netcdf-3.5.0/src > checking for m4 preprocessor > checking for m4... m4 > checking m4 flags... -B10000 > checking C compiler "/usr/bin/egcs"... works > checking how to make dependencies... false > checking for /usr/bin/g++... /usr/bin/g++ > checking C++ compiler "/usr/bin/g++"... works > checking how to run the C preprocessor... /usr/bin/egcs -E > checking user-defined Fortran-77 compiler "pgf90"... works > checking for Fortran .F compiler... > checking if Fortran-77 compiler handles *.F files... no > checking for Fortran preprocessor... /usr/bin/egcs -E > checking "pgf90" as Fortran-90 compiler... failed to build test program > checking for xlf90... no > checking for f90... no > configure: warning: Could not find working Fortran-90 compiler > configure: warning: The Fortran-90 interface will not be built > checking for nm utility > checking for nm... nm > checking nm flags... > checking for C-equivalent to Fortran routine "SUB"... sub_ > checking for Fortran "byte"... yes > checking for Fortran "integer*2"... yes > checking if Fortran "byte" is C "signed char"... configure: error: Could not > link conftestf.o and conftest.o From the above, it looks like some environment variables weren't defined correctly before the configure script was invoked. Try the following: 1. Go to the top-level source directory of the package. 2. Perform steps 3 and 4 described near the end of the file INSTALL.html 3. Set the following environment variables to the indicated values: CC=/usr/bin/gcc CPPFLAGS='-DNDEBUG -DpgiFortran' CFLAGS=-O FC=/proj/pgi/linux86/bin/pgf90 FFLAGS="-O -w" CXX=/usr/bin/g++ 4. Perform steps 6 through 9 described near the end of the file INSTALL.html. Please let me know if this helps. Regards, Steve Emmerson <http://www.unidata.ucar.edu>