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, Sorry it has taken so long to respond to your question ... > I have installed netcdf4.1.2. But it does not find the functions with prefix > nf_ > when I compile LAPS-0-46-1 software which from NOAA/ESRL/GSD. I check the > compile process of LAPS, confirm it is correct. I think maybe netcdf is not > correctly installed. I run "make check" after make it and find some errors. > But > I don't known how to solve it. Could you give some suggestions to me? > The attachment is the output of "make check" The 2 errors you see from "make check": > *** Test: varm on URL: > http://motherlode.ucar.edu:8080/thredds/dodsC/testdods/coads_climatology.nc > FAIL: test_varm3 > Error: NetCDF: I/O failure > FAIL: test_vara > ================================================ > 2 of 5 tests failed are probably the result of a failure of the test server at motherlode.ucar.edu:8080, which was moved to port 8081, rather than the netCDF library. If you would run "make clean", rerun the netCDF configure script with the option "--disable-fortran-compiler-check", and then run "make check", the tests might all succeed. So netCDF may be correctly installed. Not finding functions with prefix nf_ might be caused by several possible problems: 1. If the Fortran library was installed as a separate library, perhaps because both C and Fortran libraries were installed as shared libraries, you would need to link with both ... -lnetcdff -lnetcdf instead of just ... -lnetcdf 2. If the netCDF Fortran library were built with a different Fortran compiler than the Fortran compiler you are trying to link with, the nf_ functions might not be found, if the compilers use different conventions for calling C functions from Fortran. 3. If the 4.1.2 library were compiled without Fortran support because the configure script could not locate a working Fortran compiler or because --disable-fortran was specified as a configure option, that might be the cause of the problem. We would need more information to be able to distinguish among these or other possible sources for the problem. For example, the complete output of the library build, including config.log, output of configure, and output from "make check" might help. --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: JMX-999814 Department: Support netCDF Priority: Normal Status: Closed