[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20010425: netcdf problems

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 20010425: netcdf problems
  • Date: Thu, 26 Apr 2001 21:29:02 -0600
>From: "Julie Pietrzak" <address@hidden>
>Organization: ?
>Keywords: 200104250712.f3P7C7L01024 netCDF

Julie,

In my last reply, I wrote:

> ... The failure you saw on the test of the Fortran-90 interface is
> the same one we encountered on our Cray J90, but we don't know what
> it means:
> 
>  Making `test' in directory /tmp/jtmp.042042a/netcdf-3.5.0/src/f90
> 
>        f90 -o netcdf_test -g -F -dp  netcdf_test.f90 netcdf.o typeSizes.o 
> ../libsrc/libnetcdf.a 
> 
>    call check(nf90_put_var(ncFileID, lonVarId,     (/ -180, -175, -170 /)     
>  ) )
>             ^                                                                 
>    
>  cf90-389 f90: ERROR NETCDFTEST, File = netcdf_test.f90, Line = 78, Column = 
> 14 
>    No specific match can be found for the generic subprogram call 
> "NF90_PUT_VAR".

It turns out this is a problem with the current Fortran-90 interface
on any platform with 8-byte default Fortran integers, such as the Cray
J90.  We have no easy fix for this that would not break the Fortran-90
interface on platforms with 4-byte integers.  Thus for now the only
workaround is to get by with only the Fortran-77 interface on such
platforms ...

--Russ