Re: 19981026: netCDF on T3D/E

Al,

>Date: Fri, 30 Oct 1998 16:49:23 -0500
>From: Al Bourgeois <address@hidden>
>Organization: Lockheed Martin
>To: Steve Emmerson <address@hidden>
>Subject: Re: 19981026: netCDF on T3D/E
>Keywords: 199810292226.PAA24396

In the above message, you wrote:

> Things seem to be working fine now. It's still compiling (compilation on
> the T3D is pretty slow), but it's gotten through the fortran directory
> successfully and has proceeded to ncdump.

Great!

> Sorry for the dumb mistake,
> and thanks for the help. FYI, here is the result of the conftests for
> the T3D configuration:
> 
> checking for Fortran .F compiler... 
> checking if Fortran compiler handles *.F files... no
> checking for Fortran preprocessor... cc -E
> 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"... no
> checking if Fortran "integer*1" is C "int"... yes
> checking if Fortran "integer*1" is C "long"... yes
> checking if Fortran "integer*2" is C "short"... no
> checking if Fortran "integer*2" is C "int"... yes
> checking if Fortran "integer*2" is C "long"... yes
> checking if Fortran "integer" is C "int"... yes
> checking if Fortran "real" is C "float"... no
> checking if Fortran "real" is C "double"... 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
> 
> -Al

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