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.
Kara, Another possibility is that you built a separate Fortran library that is not in libnetcdf.a. This would happen if you invoked configure with the "--enable-separate-fortran" option, or if you specified that shared libraries should be built using the "--enable-shared" option to configure. There would have been an extra library installed that you could check for, named "libnetcdff.a". In that case, you would have to mention the extra Fortran library when linking, as in gfortran -o simple_xy_wr simple_xy_wr.o /sw/lib/netcdf/libnetcdff.a /sw/lib/netcdf/libnetcdf.a or the shorter gfortran -o simple_xy_wr simple_xy_wr.o -L/sw/lib/netcdf -lnetcdff -lnetcdf If neither of these work, then check whether the number of underscores in the external names in libnetcdf.a match the number of underscores in the undefined symbols, using something like nm -a /sw/lib/netcdf/libnetcdf.a | grep nf_close If they don't match, then may you need to "make distclean" and rerun the configure script with the CPPFLAGS environment variable set to "-DgFortran". If that still doesn't work, please let us know. (Yup, already went to the Boulder Creek Festival yesterday, and keeping up with netCDF support is one thing to do while waiting for the barbecue grill to warm up :-). --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: GAW-821062 Department: Support netCDF Priority: Normal Status: Closed