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.
Craig, >Date: Sun, 8 Oct 2000 00:58:45 -0400 >From: "Craig A. Mattocks" <address@hidden> >To: Steve Emmerson <address@hidden> >Subject: Re: 20001006: NetCDF errors on Mac OS X >Keywords: 200010050500.e9550A117969 The above message contained the following: > Nope. I'm living in Chapel Hill, NC. My parents died and I was > selected as Executor of their estate. It's a long story. Sorry to hear that. Please accept my condolences. > >I'd like to see the results of thoroughly testing the Fortran API. > >Please do the following: > > > > 1. Go to the "nf_test/" source directory. > > > > 2. Execute the command "make test". Redirect standard output and > > standard error to the file "test.log". Send me the file. > > I don't have a real Fortran 77/90 compiler, I am using netlib's f2c, > which is known to be lacking in its f90 capabilities. I've successfully built and tested the netCDF package using "f2c". > The Makefile > chokes fabulously but I was finally able to build nf_test by hand. > The tests produced zillions of errors (following). Any hope? > > Thanks! > Craig > > /nf_test/{197}> ./nf_test > *** Testing nf_strerror ... > *** Testing nf_open ... > nf_open: No such file or directory > nf_redef of read-only file should fail > nf_open: No such file or directory > nf_close: Not a netCDF id ... The above indicates an initial failure of the Fortran API -- it expects a netcdf test-file to exist but it doesn't. If you look in the Makefile, you'll see that the command "./nf_test -c" must be executed before the command "./nf_test". The "-c" version of the command creates an initial test-file. Would you please send me the first page of output (both standard output and standard error) from the following $ cd nf_test $ ./nf_test -c $ ./nf_test Regards, Steve Emmerson <http://www.unidata.ucar.edu>