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 Gaby, re: try the following invocation command line: ifort -g -L/home/turekg/local/lib -lnetcdf -o a.out *.f90 > Nope, this does not work either, I get all sorts of error messages, > mostly having to do with the calls to netcdf functions This behavior is similar to a situation I ran into on DEC OSF/1 where I had to specify search of a (non-netcdf) library doing the same thing as you. Just as a sanity check (for me, not you) can you let me know the result of the following: locate libnetcdf and ifort -g *.f90 -o a.out -L/home/turekg/local/lib -lnetcdf If the slightly reformulated compile/link line still results in undefined Fortran externals, try adding the '-lnetcdf' again: ifort -g *.f90 -o a.out -L/home/turekg/local/lib -lnetcdf -lnetcdf I don't expect this to work, but it might give us some clues as to what is going on if the list of undefined externals changes. Cheers, Tom **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: EZD-873215 Department: Support netCDF Priority: Normal Status: Closed