20010828: building netCDF 3.5 under Linux-PC

Lars,

> To: address@hidden
> From: Lars Umlauf <address@hidden>
> Organization: ?
> Keywords: 200108281206.f7SC6R101365 netCDF 3.5 Linux-PC

The above message contained the following:

> Hello everybody,
> 
> I tried to compile the netCDF library on a Linux-PC (nothing=20
> special), but it didn't work. I copied all the files you require to=20
> have in such cases in inserted them in this e-mail below. Maybe you=20
> can help me.
> 
> Thanks,
> 
> Lars
> 
> VERSION:
> 
> 3.5.0
> 
> -----------------------------
> 
> uname:
> 
> Linux mira.mechanik.tu-darmstadt.de 2.2.17-21mdk #1 Thu Oct 5=20
> 13:16:08 CEST 2000 i686 unknown
> -----------------------------------------------------
> 
> configure.log:
> 
> creating cache ./config.cache
> checking for top-level source-directory
> /usr/local/src/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++"... works
> checking how to run the C preprocessor... /usr/bin/gcc -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 progr=
> am
> 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"... 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

The above file "configure.log" doesn't indicate any problem, so I don't
need to see the file "config.log".

You didn't send me the file "make.log", however.  Would you please send
that to me so that I can see the problem.

One thing: on a Linux system, it is necessary to define the C macro 
"f2cFortran" before executing the configure script, e.g.

    CPPFLAGS=-Df2cFortran ... ./configure >configure.log 2>&1

If you don't, then the Fortran interface won't be built correctly.

Regards,
Steve Emmerson   <http://www.unidata.ucar.edu>