>Just that what is necessary for users to link with the (shared) >libnetcdf.so should not change based on whether netcdf was configured >with --enable-netcdf-4 (or --with-szlib) Ok, I see. I did a build here with (I think) the same set of ./configure parameters as in you example, namely: CC=mpicc; export CC CXX=mpicxx; export CXX FC=mpif90; export FC F77=mpif77; export F77 ./configure --prefix=... --enable-shared --enable-netcdf-4 \ --disable-dap --with-hdf5=... --with-zlib=... and machine info (via uname -a) Linux spock.unidata.ucar.edu 2.6.27.35-170.2.94.fc10.x86_64 #1 SMP Thu Oct 1 1\ 4:41:38 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux This produced a libnetcdf.so with the following ldd output. You can see that libhdf5 is referenced. So at this point, I am baffled as to why mine has it and yours does not. ldd libnetcdf.so linux-vdso.so.1 => (0x00007fffc070e000) libhdf5_hl.so.6 => /upc/share/stdinstall/local/spock/lib/libhdf5_hl.so\ .6 (0x00007fad181dd000) libhdf5.so.6 => /upc/share/stdinstall/local/spock/lib/libhdf5.so.6 (0x\ 00007fad17c2f000) libmpich.so.1.1 => /usr/lib64/mpich2/libmpich.so.1.1 (0x00007fad1787b0\ 00) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fad17645000) librt.so.1 => /lib64/librt.so.1 (0x00007fad1743b000) libc.so.6 => /lib64/libc.so.6 (0x00007fad170c9000) libz.so.1 => /upc/share/stdinstall/local/spock/lib/libz.so.1 (0x00007f\ ad16eb2000) libm.so.6 => /lib64/libm.so.6 (0x00007fad16c2c000) /lib64/ld-linux-x86-64.so.2 (0x0000003ca1a00000) Ticket Details =================== Ticket ID: NBS-392373 Department: Support netCDF Priority: High Status: Open