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.
Mark, Yesterday, I wrote: > First I built and installed HDF5 with --prefix=${H5DIR}. > Then I built and installed HDF4 with > > ./configure --enable-shared --disable-netcdf --disable-fortran > --prefix=${H4DIR} > make > make install > > Then for netCDF-4.1.3 (and this probably works for later versions as well), I > used > > CPPFLAGS="-I${H5DIR}/include -I${H4DIR}/include -I/opt/include" > LDFLAGS="-L${H5DIR}/lib -L${H4DIR}/lib -L/opt/lib" ./configure > --disable-shared --enable-hdf4 --enable-hdf4-file-tests > > and make check completed with no errors. It also worked fine with > "--disable-dap", > but I had the necessary libcurl previously installed in /opt/lib, so I > verified that > it works with DAP client access. The HDF-4 file tests also completed > successfully. I was curious whether the "--disable-shared" for the netCDF build that enabled HDF4 access was really needed. It turns out that it's not. Everything builds and the tests run successfully in both netCDF 4.1.3 and the current 4.3.0 release candidate when built as a shared library, as long as HDF4 is built with "--disable-netcdf". --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: VOG-153523 Department: Support netCDF Priority: Normal Status: Closed