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 Raphal Martin, Sorry it has taken so long to respond to your question. Were gcc and gfortran compilers used when the library was built and installed? Was "make check" run successfully after the library was built? If so, there are some example Fortran programs in the sources, in the directory examples/F90 that should have been built and checked when "make check" was run. If you could run "make check" in that directory, it would check if the Fortran interface was built correctly. The programs you are compiling are looking for library functions with names that end in two underscores, such as `nf_create__'. It would also be helpful to look what function names are provided by the installed library, in your case /usr/lib/libnetcdff.a, with a command like nm -a /usr/lib/libnetcdff.a | grep nf_create If the library only provides names ending in one underscore, that indicates a problem in the compiler used to build the library using a different convention for names than the compiler you are using. For example, I believe older versions of gfortran used a different number of trailing underscores than more recent versions of gfortran. --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: LSZ-331741 Department: Support netCDF Priority: Normal Status: Closed