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.
Greetings Irena! `make check` is looking for nf_*_ symbols (e.g. nf_open_) but can't find them because they are set as nf_*__ (two appended underscores instead of one). It may be the case that the configure script does not recognize `gfortran4` and is not able to set the proper flags. Try the following: make distclean export CPPFLAGS=-DgFortran and then run config, make, and make check. Also, is gfortran4 the name of the actual fortran compiler, or is it a symlink to a specific version of gfortran (ls -l /usr/pppl/gcc/4.6.0/bin/gfortran4 will tell you)? Thanks! Sean > Hi Sean, > > Thank you for your help last week, could you tell me what is wrong here? > > > readelf -Ws /local/ijohnson/netcdf-4.1.2/fortran/.libs/libnetcdff.so |grep > nf_open > 236: 0000000000000000 0 NOTYPE GLOBAL DEFAULT UND nf_open_ > 523: 000000000000c050 240 FUNC GLOBAL DEFAULT 10 nf_open__ > 307: 0000000000000000 0 NOTYPE GLOBAL DEFAULT UND nf_open_ > 594: 000000000000c050 240 FUNC GLOBAL DEFAULT 10 nf_open__ > > > Irena > On Jun 3, 2011, at 3:24 PM, Unidata netCDF Support wrote: > > > Hi Irena, > > > >> Hi Sean, > >> > >> here is the output: > >> ijohnson@sunfire20>$pwd > >> /local/ijohnson/netcdf-4.1.2/fortran/.libs > >> > >> readelf -Ws /usr/lib64/libnetcdff.so.5.0.0 | grep nf_open > >> readelf: Error: '/usr/lib64/libnetcdff.so.5.0.0': No such file > > > > So sorry about that - libnetcdff.so.5.0.0 was specific to my machine, and > > since I have it installed on my system, it lives in /usr/lib64. Could you > > try the command on libnetcdff.so in your local build directory? > > > > readelf -Ws /local/ijohnson/netcdf-4.1.2/fortran/.libs/libnetcdff.so > > > > Once built and installed, libnetcdff.so will likely end up in /usr/lib64 > > (unless you specified a --prefix option in ./configure), but since it's not > > built and installed yet, it will live in the build directory > > /local/ijohnson/netcdf-4.1.2/fortran/.libs/ > > > > Thanks! > > > > Sean > > > >> > >> > >> It looks like it takes the wrong path for libnetcdff* > >> > >> ijohnson@sunfire20>$pwd > >> /local/ijohnson/netcdf-4.1.2/fortran/.libs > >> ijohnson@sunfire20>$ls > >> fort-attio.o fort-geninq.o fort-v2compat.o fort-varmio.o > >> libnetcdff.lai > >> fort-control.o fort-genvar.o fort-var1io.o fort-varsio.o > >> libnetcdff.so > >> fort-dim.o fort-lib.o fort-varaio.o libnetcdff.a > >> libnetcdff.so.5 > >> fort-genatt.o fort-misc.o fort-vario.o libnetcdff.la > >> libnetcdff.so.5.1.0 > >> > >> > >> > >> Thanks for helping, > >> Irena > >> > >> > >> On Jun 3, 2011, at 2:52 PM, Unidata netCDF Support wrote: > >> > >>> readelf -Ws /usr/lib64/libnetcdff.so.5.0.0 | grep nf_open > >> > >> > > > > > > Ticket Details > > =================== > > Ticket ID: AIX-484936 > > Department: Support netCDF > > Priority: Normal > > Status: Open > > > > Ticket Details =================== Ticket ID: AIX-484936 Department: Support netCDF Priority: Normal Status: Open