Hi Mike, > I need some help building the latest netcdf release. > > Previously I was building netcdf-4.1.1, along with hdf5 support, as follows: > > tar xvfz hdf5-1.8.10-patch1.tar.gz > cd hdf5-1.8.10-patch1 > configure --prefix=/tmp/netcdf > make -j 4; make install > cd .. > > tar xvfz netcdf-4.1.1.tar.gz > cd netcdf-4.1.1 > ./configure --enable-netcdf-4 --with-hdf5=/tmp/netcdf > --prefix=/tmp/netcdf --disable-dap > make -j 4; make install > > and that worked. But with the latest version I did: > > tar xvfz netcdf-220.127.116.11.tar.gz > cd netcdf-18.104.22.168 > ./configure --enable-netcdf-4 --with-hdf5=/tmp/netcdf > --prefix=/tmp/netcdf --disable-dap > > and I get the following error: > > checking for library containing H5Fflush... no > configure: error: Can't find or link to the hdf5 library. Use > --disable-netcdf-4, or see config.log for errors. > > I have attached config.log. > > Could you please advise? Starting with version 4.1.3, use of "--with-hdf5=/dir/for/hdf5" was dropped as a configure option, because The use of the --with-hdf5 option (and similar ones like --with-zlib, --with-szlib, --with-pnetcdf, --with-hdf4) caused two serious bugs: 1 - No way for these options to work on platforms that have libraries in /lib and /lib64 for 32 and 64 bit builds. 2 - Caused problem for cross-compiles like the mingw32 build and builds on some supercomputers. So the way to specify where HDF5 is installed now uses the configure arguments (or environment variables) CPPFLAGS=/dir/for/hdf5/include and LDFLAGS=/dir/for/hdf5/lib , as described here: http://www.unidata.ucar.edu/software/netcdf/docs/build_default.html --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: PSD-701995 Department: Support netCDF Priority: Normal Status: Closed
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.