Re: compiling with f90

• To: "Sandy L. King" <sking@xxxxxxxxxxxx>
• Subject: Re: compiling with f90
• From: Russ Rew <russ@xxxxxxxxxxxxxxxx>
• Date: Thu, 13 May 1999 09:58:37 -0600

Sandy L. King <sking@xxxxxxxxxxxx> wrote:

> We are having trouble finishing the installation of the NetCDF package
> using the Fortran 90 compiler.  The NetCDF code seems to compile ok,
> but when we run "make test", it runs until it begins testing the
> nf_get* and nf_set* functions.  At that point we get numerous "Numeric
> conversion not representable" errors.  When we use the Fortran 77
> compiler the tests run fine.  Has anyone encountered this problem
> before?
> 
> This is the result of a "uname -a" command:
> 
> SunOS mish 5.6 Generic_105181-05 sun4u sparc SUNW,Ultra-5_10
> 
> 
> These are the settings I am using:
> 
> CC=/opt/SUNWspro/bin/c89
> CPPFLAGS=-DNDEBUG
> CFLAGS=-O
> FC=/opt/SUNWspro/bin/f90
> FPP=/opt/SUNWspro/bin/fpp
> FPPFLAGS=-D__SUNPRO_F90
> COMPILE_F
> FFLAGS="-O -w"
> CXX=/opt/SUNWspro/bin/CC

I can't duplicate the problem.  I built netCDF-3.4 using the
environment variable settings you are using on a very similar
platform.  Output from "uname -a" is:

  SunOS zero.unidata.ucar.edu 5.6 Generic_105181-12 sun4u sparc SUNW,Ultra-2

The version of f90 we have installed (output from "f90 -V") is:

  f90: WorkShop Compilers 4.2 01 Dec 1997 FORTRAN 90 1.2 patch 104366-04

The "make all" and "make test" worked fine, with no errors.  I also
tested f90 on a SunOS 5.7 platform with the same settings, and it
worked also.

All I can suggest is to make sure your Fortran 90 compiler patch level
is up to date, and try running the tests on a local disk, in case there
is an NFS configuration problem that this test is revealing.  Also
check the console for any I/O errors ...

--Russ

_____________________________________________________________________

Russ Rew                                         UCAR Unidata Program
russ@xxxxxxxxxxxxxxxx                     http://www.unidata.ucar.edu