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.
Hi Dick, > I need a little help, if you can give it to me. We installed 2.4.2 > yesterday, and due to an installation error independent of netcdf, > the products weren't available for a short while. I think they are, > but I have no little test to run. "make test" won't work because I need > root privileges to test the stuff within /usr/local and I don't have 'em. You can build netcdf in your own directory and run tests in any of the libsrc/, nctest/, fortran/, ncdump/, ncgen/, or cxx/ subdirectories by changing to the subdirectory, running "make clean test" to observe how it is compiled and linked, then compile and link the same way except refer to the include files and libraries in /usr/local/ instead of the ones in your directory. Another way to do the same thing would be to build netcdf in your local directory but then replace the locally-built libraries, include files, and executables with links to the ones in /usr/local/, then run make test to verify that everything works with the installed copies. > I tried compiling a little program > > INCLUDE 'netcdf.inc' > call putgetg > call sharray > end > > to see if I could load the routines, but cf77 complained > > cft77-360 cf77: ERROR , Line = 1, File = junk.f, Line = 1 > Unable to open file named in INCLUDE line. > > even though /usr/local/include/netcdf.inc is in place. You probably would have needed the appropriate -I/usr/local/include/ flag to the Fortran compiler so it would have known where to look. Good luck. --Russ