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.
Tim, Here's a suggestion that might help isolate the problem. Since you can link with an f90 example program that calls both nf90_strerror and nf90_open, try adding some of the other object files to the link line for that program to see if you get the unsatisfied external error. For example, since gfortran -g -O2 pres_temp_4D_rd.o ../../libsrc/.libs/libnetcdf.a -o pres_temp_4D_rd works fine for you and results in a working executable, try copying your handle_err.o into the same directory and invoking gfortran -g -O2 handle_err.o pres_temp_4D_rd.o ../../libsrc/.libs/libnetcdf.a -o pres_temp_4D_rd If that doesn't give you an unsatisfied external, add more of the object files you are trying to link together until you see the error. That should provide a clue to whether your guess that some other library or object file is causing the problem is correct. --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: FTD-335729 Department: Support netCDF Priority: Normal Status: Closed