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.
Paola, > From: Paola Petrelli <address@hidden> > Organization: ? > Keywords: 200203141006.g2EA6ma12180 netCDF 3.5 install The above message contained the following: > I have a problem with the installation of netcdf > > [root@antar89142 src]# uname -a > Linux antar89142 2.4.3-20mdk #1 Sun Apr 15 23:03:10 CEST 2001 i686 unknown > > VERSION: 3.5.0 > > pathnames of compilers: > /usr/bin/cc > /usr/bin/g++ > /usr/bin/g77 > > CONFIGURE.LOG: > > creating cache ./config.cache > checking for top-level source-directory > /home/newmar/Netcdf/netcdf-3.5.0/src > checking for m4 preprocessor > checking for m4... m4 > checking m4 flags... -B10000 > checking C compiler "/usr/bin/cc"... 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/cc -E > checking user-defined Fortran-77 compiler "/usr/bin/g77"... works > checking for Fortran .F compiler... > checking if Fortran-77 compiler handles *.F files... yes > checking "/usr/bin/g77" as Fortran-90 compiler... failed to build test program > checking for xlf90... no > checking for f90... no > 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"... yes > checking if Fortran "byte" is C "short"... no > checking if Fortran "byte" is C "int"... no > checking if Fortran "byte" is C "long"... no > checking if Fortran "integer*2" is C "short"... yes > checking if Fortran "integer*2" is C "int"... no > checking if Fortran "integer*2" is C "long"... no > checking if Fortran "integer" is C "int"... yes > checking if Fortran "real" is C "float"... yes > checking if Fortran "doubleprecision" is C "double"... yes > checking for Fortran-equivalent to netCDF "byte"... byte > checking for Fortran-equivalent to netCDF "short"... integer*2 > checking for math library > checking for tanh in -lc... no > checking for tanh in -lm... yes > 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... yes > checking for working ftruncate()... yes > checking for working alloca.h... yes > checking for alloca... yes > checking for st_blksize in struct stat... yes > checking for IEEE floating point format... yes > checking for ANSI C header files... yes > checking for size_t... yes > checking for off_t... yes > checking for ssize_t... yes > checking for ptrdiff_t... yes > checking for uchar... no > checking whether char is unsigned... no > checking whether byte ordering is bigendian... no > checking size of short... 2 > checking size of int... 4 > checking size of long... 4 > checking size of float... 4 > checking size of double... 8 > checking size of off_t... 4 > checking size of size_t... 4 > 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 I don't see a problem in the above. Would you please send me the file "make.log", which is described near the end of the file INSTALL.html. Regards, Steve Emmerson <http://www.unidata.ucar.edu>