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

Re: 19980715: Fortran interface: NF_INT_IS_C_... not defined

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: 19980715: Fortran interface: NF_INT_IS_C_... not defined
  • Date: Tue, 04 Aug 1998 09:03:38 -0600
Reinhard,

Sorry for taking so long to respond.

>Date: Wed, 15 Jul 1998 13:10:04 -0600 (MDT)
>From: "Reinhard W. Stotzer" <address@hidden>
>Organization: Sandia National Laboratory
>To: Steve Emmerson <address@hidden>
>Subject: Re: 19980715: Fortran interface: NF_INT_IS_C_... not defined 
>Keywords: 199807151505.JAA17877

In the above message, you wrote:

>    This seems to work!! I can't tell yet, whether I'll still run into
> problems trying to interface with other codes or not, but at least I
> don't get any error messages in the compilation process. I guess, it
> wouldn't hurt to read the INSTALL file more carefully...
> 
>    I have another problem on a DEC Alpha (running OSF V4.0). The
> compilation works fine, except for some warnings about a mismatch in
> type (I've included the make.log and other files again), but then I run
> into problems trying to connect netCDF with an application code. 
> The application must read a file written by a direct fortran write,
> then write an exodus/netcdf file. It must have 32 byte integers to read
> the direct access file. However, I get memory alignment errors in that
> case in the netcdf routines. It appears that the only way to get away from
> the alignment problem is to compile the routines with -integer_size 64. 
> 
>   Can you provide me with any help on this?

The handling of alignment errors on a DEC Alpha can be controlled via
the uac(1) utility.  Check the uac(1) manual-page for more information.

>   Anyway, many thanks for your help with my problem on the CRAY!

You're welcome.

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