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.
>To: address@hidden >From: "James K Lewis" <address@hidden> >Subject: Re: 20040311: netCDF for W2K >Organization: Scientific Solutions, Inc. >Keywords: 200403110123.i2B1NgrV000584 Hi Jim, > Russ: I've made progress on the Win32 netcdf problem. I now have used my > Lahey compiler to generate typesizes.mod and netcdf.mod files without any > errors or warnings. I did change all the *.f90 files from Unix formats > (line feed only at the end of a line) to DOS formats (line feed and carriage > control). Great, I'm glad it was that simple. > Now I'm trying to compile and link netcdf_test.f90. In the netcdf-f90win32 > zip file, there are 4 library files. Two get unzipped into a bin directory > (f90netcdf.lib and netcdf.dll) and 2 get unzipped into a lib directory > (again f90netcdf.lib and netcdf.lib). When I link, where do I go to pick up > the netcdf libraries? Do I need to specify both files in the bin or lib > directories? I think the library files that got unzipped into the bin directory were a mistake. The library files should be accessed from the lib directory. The only things that should be in the bin directory are the ncdump.exe and ncgen.exe executables, which you don't need to link the test. I suspect the guy who created this zip file meant to put ncdump.exe and ncgen.exe in the bin directory. --Russ -----Original Message----- Russ: I have now generated typesizes.mod and netcdf.mod files using the Lahey F90 compiler. When I compile the netcdf.f90 file, I get 140 warnings from the netcdf_overloads.f90 file stating something along the lines of "Specific procedures (nf90_put_att_onebyteint) and (nf90_put_att_twobyteint) do not insure that the generic procedure (nf90_put_att) is unambiguous" I get these for the various names in netcdf_overloads.f90 for interface nf90_put_att, interface nf90_get_att, interface nf90_put_var, and interface nf90_get_var. When I try to compile netcdf_test.f90 with the *.mod files, I get 8 errors that state "Generic procedure reference must be unambiguous for nf90_put_att" for line 52 "Generic procedure reference must be unambiguous for nf90_put_att" for line 55 "Generic procedure reference must be unambiguous for nf90_put_var" for line 86 "Generic procedure reference must be unambiguous for nf90_put_var" for line 87 "Generic procedure reference must be unambiguous for nf90_put_var" for line 91 "Generic procedure reference must be unambiguous for nf90_put_var" for line 97 "Generic procedure reference must be unambiguous for nf90_put_var" for line 98 "Generic procedure reference must be unambiguous for nf90_put_var" for line 100 So sometimes it knows what to do with nf90_put_att or nf90_put_var and sometimes it doesn't. How can I overcome the warnings in netcdf.f90 or the errors in nectcdf_test.f90? James Lewis