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.
Florence, >Date: Thu, 25 Sep 2003 17:32:45 +0200 >From: "Florence Troude" <address@hidden> >Organization: COPARLY >To: "'Steve Emmerson'" <address@hidden> >Subject: RE: 20030924: netcdf installation problem The above message contained the following: > Steve, > You're right. > here are the correct files. sorry. > bests, > Florence > > __________________________________________ > configure.log : > creating cache ./config.cache > checking for top-level source-directory > /usr/local/netcdf-3.5.0/src > checking for m4 preprocessor > checking for m4... m4 > checking m4 flags... -B10000 > checking C compiler "/usr/bin/gcc"... works > checking how to make dependencies... false > checking for /usr/bin/g++... /usr/bin/g++ > checking C++ compiler "/usr/bin/g++"... configure: warning: /usr/bin/g++ > failed on test program > configure: warning: Could not find working C++ compiler > configure: warning: Setting CXX to the empty string > configure: warning: The C++ interface will not be built > checking how to run the C preprocessor... /usr/bin/gcc -E > checking user-defined Fortran-77 compiler " "... failed to compile test > program > configure: warning: The Fortran-77 interface will not be built > checking for Fortran .F compiler... > checking for Fortran preprocessor... /usr/bin/gcc -E > checking user-defined Fortran-90 compiler " "... failed to compile test > program > configure: warning: The Fortran-90 interface will not be built > checking for nm utility > checking for nm... nm > checking nm flags... > checking for math library > checking for tanh in -lc... no > checking for tanh in -lm... no > checking for ar utility > checking for ar... ar > checking ar flags... cru > checking for nm utility > checking for nm... (cached) nm > checking nm flags... > checking for ranlib... ranlib > checking for stdlib.h... yes > checking for sys/types.h... yes > checking for strerror... no > checking for working ftruncate()... no > checking for working alloca.h... no > checking for alloca... no > checking whether alloca needs Cray hooks... no > checking stack direction for C alloca... -1 > checking for st_blksize in struct stat... yes > checking for IEEE floating point format... no > checking for ANSI C header files... no > checking for size_t... yes > checking for off_t... yes > checking for ssize_t... yes > checking for ptrdiff_t... no > checking for uchar... no > checking whether char is unsigned... no > checking whether byte ordering is bigendian... no > checking size of short... 0 > checking size of int... 0 > checking size of long... 0 > checking size of float... 0 > checking size of double... 0 > checking size of off_t... 0 > checking size of size_t... 0 > checking for manual-page index command... > checking binary distribution directory... /home/ftp/pub/binary/dummy_system > updating cache ./config.cache > creating ./config.status > creating macros.make > udcreating fortran/nfconfig.inc > creating libsrc/ncconfig.h The above looks OK. The resulting netCDF library won't have a C++, Fortran-77, or Fortran-90 interface, but the C interface should be OK. If the lack of the C++ and Fortran interfaces is acceptable, then I suggest continuing with the rest of the build and installation: 1. Go to the top-level source directory. 2. Perform steps 7 through 9 which are described near the end of the file INSTALL.html. Please let me know of any problems. Regards, Steve Emmerson