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.
Eric, > From: eric Mena <address@hidden> > Subject: Problem using netcdf > Organization: Fujitsy Systems europe > Keywords: 200006141339.e5EDdKT15263 netCDF Fujitsu VPP5000 In the above message, you wrote: > I am using netcdf on a Fujitsu VPP5000 machine. > I compiled netcdf library both in 64 address mode and 32 address mode, > for both of them "make test" works with no errors. > I have a program that generate a netcdf file that works when compiled in > 32 address mode but fails when compiled in 64 address mode. > Using the debugger I could see that after using > NF_CREATE,NF_DEF_DIM,NF_DEF_VAR,NF_PUT_ATT_TEXT and NF_ENDDEF the code > fails in NF_PUT_VAR_REAL because routine > putNCv_float(ncp,varp,coord_zero,*varp->dsizes,value) is called with > coord_zero[0] equal to 8551279886337 which is a stupid value. I'll need some more information in order to diagnose the problem. On your system, 1. What is the size of a Fortran Real in 32-bit mode? In 64-bit mode? 2. What is the size of a C float in 32-bit mode? In 64-bit mode? Also, would you please send me the following: 1. The file "configure.log" from building the netCDF package in 32-bit mode and in 64-bit mode. 2. The file "fortran/nfconfig.inc" from building the netCDF package in 32-bit mode and in 64-bit mode. Regards, Steve Emmerson <http://www.unidata.ucar.edu>