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.
Dan, >Date: Mon, 30 Aug 1999 11:04:12 -0400 (EDT) >From: Dan Codiga <address@hidden> >Organization: University of Connecticut, Avery Point Campus >To: Steve Emmerson <address@hidden> >Subject: Re: 19990823: installing netCDF-3.4 on Linux >Keywords: 199908301437.IAA09536 In the above message, you wrote: > I ran > > ./configure >&! config.stderr ... > A copy is appended below. > > Dan > > > > > On Mon, 30 Aug 1999, Steve Emmerson wrote: > > > > Would you please send me the standard output and standard error from > > executing the configure script. > > > > ------------------------- > > loading cache ./config.cache > checking for m4... (cached) m4 > checking for xlc... (cached) cc > checking C compiler... works > checking how to make dependencies... false > checking for CC... (cached) c++ > checking C++ compiler "c++"... works > checking how to run the C preprocessor... (cached) cc -E > checking for f77... (cached) f77 > checking for Fortran .F compiler... > checking if Fortran compiler handles *.F files... yes > 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 -lc... (cached) no > checking for -lm... (cached) yes > checking for ar... (cached) ar > checking for ranlib... (cached) ranlib > checking for stdlib.h... (cached) yes > checking for sys/types.h... (cached) yes > checking for strerror... (cached) yes > checking whether cross-compiling... (cached) no > checking for working ftruncate()... yes > checking for working alloca.h... (cached) yes > checking for alloca... (cached) yes > checking for st_blksize in struct stat... (cached) yes > checking for IEEE floating point format... yes > checking for ANSI C header files... (cached) yes > checking for size_t... (cached) yes > checking for off_t... (cached) yes > checking for ssize_t... (cached) yes > checking for ptrdiff_t... (cached) yes > checking for uchar... (cached) no > checking whether char is unsigned... (cached) no > checking whether byte ordering is bigendian... (cached) no > checking size of short... (cached) 2 > checking size of int... (cached) 4 > checking size of long... (cached) 4 > checking size of float... (cached) 4 > checking size of double... (cached) 8 > checking size of off_t... (cached) 4 > checking size of size_t... (cached) 4 > checking for manual-page index command... > checking binary distribution directory... /home/ftp/pub/binary/dummy_system > creating ./config.status > creating macros.make > udcreating fortran/nfconfig.inc > fortran/nfconfig.inc is unchanged > creating libsrc/ncconfig.h > libsrc/ncconfig.h is unchanged OK. If you're using the native "cc" and "f77" compilers on Linux, then you should ensure that the CFLAGS environment variable contains the string "-Df2cFortran" before executing the configure script (for an example, see the INSTALL file; search for "Linux"). Try the following: 1. Go to the top-level source directory. 2. Perform steps 2 through 5 near the end of the INSTALL file. 3. Ensure that the CFLAGS environment variable contains the string "-Df2cFortran". 4. Perform steps 6 though 9 near the end of the INSTALL file. Please let me know if this helps. -------- Steve Emmerson <http://www.unidata.ucar.edu>