Re: 980304: netcdf Linux Installation problems

Michael,

>Date: Thu, 5 Mar 1998 14:57:50 -0500 (EST) 
>From: address@hidden
>Organization: NASA/GSFC
>To: address@hidden (Steve Emmerson)
>Subject: Re: 980304: netcdf Linux Installation problems 
>Keywords: 199803041947.MAA25833

In the above message, you wrote:

>     Replacing g77 with fort77 cured the configure script error, as you
>   suggested.

Great!

>   I have been using g77 because of its speed relative to
>   fort77/f2c. We've noticed a factor of two speed difference between
>   the two compilers on our problems.

In the speed of compilation or in the speed of program execution?

>   In light of that, I've placed 
>   netcdf on one of our smaller Linux boxes and left g77 on the big
>   machine we use for computation. Netcdf will be used for GMT. I've
>   heard that Version 3 of netcdf can be difficult to get to work
>   with GMT and that Version 2 may be preferable. Any thoughts?

I don't handle GMT questions.  The fellow who does says that he's
answered about 20 questions from GMT users trying to use netCDF 3.  He
says he answers their questions and then never hears from them again.
He doubts that there's much of a problem.

>   P.S. I've attached the successful configure.log file below:
> 
> creating cache ./config.cache
> checking for m4... m4
> checking user-defined C compiler "/usr/bin/cc"
> checking C compiler... works
> checking how to make dependencies... false
> checking for /usr/bin/c++... /usr/bin/c++
> checking C++ compiler "/usr/bin/c++"... works
> checking how to run the C preprocessor... /usr/bin/cc -E
> checking user-defined FORTRAN compiler "/usr/bin/fort77"... works
> 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 "integer*2" is C "short"... yes
> checking if FORTRAN "integer*2" is C "int"... 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... no
> checking for -lm... yes
> checking for ar... ar
> checking for ranlib... ranlib
> checking for stdlib.h... yes
> checking for sys/types.h... yes
> checking for strerror... yes
> checking for ftruncate... yes
> checking for st_blksize in struct stat... yes
> checking whether cross-compiling... no
> 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

Looks good.

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