971007: NetCDF 3.3.1: Installing on CRAYC90 with CF77

Son in Sun,

>Date: Tue, 07 Oct 1997 22:10:34 -0700 
>From: Son In Sun <address@hidden>
>Organization: Atmospheric Sciences, Yonsei University 
>To: address@hidden
>Subject: Installation on CRAYC90 
>Keywords: 199710060659.AAA16795

In the above message, you wrote:

> I mailed you about installing netCDF-3.3.1 on C90.
>  but, CRAY C90 which I use doesn't have fortran 90 
>  compiler. That only has CF77 compiler.....
> 
>  I attached some files about configurations to this
>  mail. please refer to these files and then mail me.
> 
>  When ./configure is executed, standard output data
>  is config.dat.
> 
>  Can I install netCDF3.3.1 on a C90 in CF77 environ-
>  ment?

I don't know if netCDF 3.3.1 can be built on a Cray C90 that uses cf77
rather than f90.  I suspect the answer is yes but we'll have to try to
find out.

>  If it is impossible, can previous version of netcdf 
>  be installed on the same frame?

See previous reply.

> creating cache ./config.cache
> checking for m4... m4
> checking user-defined C compiler "/bin/c89"
> checking C compiler... works
> checking how to make dependencies... false
> checking for CC... CC
> checking C++ compiler "CC"... works
> checking how to run the C preprocessor... /bin/c89 -E
> checking user-defined FORTRAN compiler "/bin/cf77"... 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"... no
> checking for FORTRAN "integer*1"... yes
> checking for FORTRAN "integer*2"... yes
> checking if FORTRAN "integer*1" is C "signed char"... no
> checking if FORTRAN "integer*1" is C "short"... yes
> checking if FORTRAN "integer*1" is C "int"... yes
> checking if FORTRAN "integer*2" is C "short"... yes
> checking if FORTRAN "integer*2" is C "int"... yes
> 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"... integer*1
> checking for FORTRAN-equivalent to netCDF "short"... integer*2
> checking for math library
> checking for -lc... yes
> checking for ar... ar
> checking for 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... no
> 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... yes
> checking whether char is unsigned... yes
> checking whether byte ordering is bigendian... yes
> checking size of short... 8
> checking size of int... 8
> checking size of long... 8
> checking size of float... 8
> checking size of double... 8
> checking size of off_t... 8
> checking size of size_t... 8
> checking for catman... no
> checking for makewhatis... no
> 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
> fortran/nfconfig.inc is unchanged
> creating libsrc/ncconfig.h
> libsrc/ncconfig.h is unchanged

The above output from executing the configure script looks good.

Would you please send me the standard output and error output from
executing the command "make" and, if that command succeeds, the command
"make test".

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