Hi Irena, > Hi Sean, > > here is the output: > address@hidden>$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* > > address@hidden>$pwd > /local/ijohnson/netcdf-4.1.2/fortran/.libs > address@hidden>$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
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.