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.
You might try these commands to see if H5Fflush is in fact defined. nm libhdf5.so |fgrep H5Fflush and nm libhdf5_hl.so | fgrep H5Fflush =Dennis Heimbigner Unidata On 4/11/2016 3:29 PM, Ward Fisher wrote: > New Staff Reply: H5Fflush not found > > Hi, > > Thanks for confirming the presence of libdl; that helps dial things in. > Looking at the file you attached, it still looks like it might be the > `configure` script? When configure is run, it generates a file > `config.log` (note that it's config, not configure). You shouldn't need to > capture any output or anything. The main thing `config.log` gives us is > that it's very readable, particularly compared to the `configure` script, > and contains more information than the output sent by the configure script > to standard output. > > I've attached a sample config.log file so you can see what I'm talking > about. If you can locate and send off the config.log from your build > attempt, I will take a look and see if I can sort this out! > > Have a great day, > > -Ward > > > > address@hidden> wrote: > >> New Client Reply: H5Fflush not found >> >> Thanks for the very fast turn around! >> >> I attach the correct version of configure.log - or at least - one that >> finishes with a non-zero exit... >> >> I would be kind of surprised if libdl wasn't present. Indeed - on /lib >> I find: >> >> -rwxr-xr-x 1 root root 20668 May 30 2013 libdl-2.5.so >> lrwxrwxrwx 1 root root 12 Dec 29 2012 libdl.so.2 -> libdl-2.5.so >> >> -jrm >> >> >> On 04/11/2016 03:35 PM, Unidata netCDF Support wrote: >>> Hello James, >>> >>> Thanks for providing all of the information; as you've deduced, the HDF5 >> library 1.8.8 is too old to use with modern netCDF. 1.8.9 is the minimum >> version required, and 1.8.16 should work just fine. It appears that you do >> not have `libdl` installed on your system. If this is the case, you can >> either install it, or, if hdf5 was built without dynamic-loading support, >> you should be able to pass `--disable-dynamic-loading` (instead of using >> LIBS=-ldl). If libdl is present, `configure` should find it itself, and >> you wouldn't need to force inclusion via `LIBS`. >>> It looks like the file you attached, ` Config_4.3.3.1.log`, is actually >> the `configure` script and not the generated `config.log` file generated >> when you ran configure. If you provide the config.log file I can look at >> it to confirm my suspicions, or you can try my suggestions and let me know >> if they work, fail, or if the symptoms change. >>> I hope this helps, >>> >>> -Ward >>> >>>> I'm trying to build a newer version of NETCDF and am encountering the >>>> H5Fflush failure on configure. Specifically: >>>> >>>> checking for library containing H5Fflush... no >>>> >>>> I'm trying to work forward from an older NETCDF build that worked, to >>>> something newer. >>>> >>>> * Our last working build of NETCDF was 4.2.1.1, using HDF5 1.8.8. I >>>> was able to reproduce this. >>>> * I obtained the HDF 1.8.16, and was also able to use that to repeat >>>> the 4.2.1.1 build >>>> * Substituting in the NETCDF 4.3.3.1 archive in the procedure that >>>> built 4.2.1.1 yields the configure failure >>>> * I observed the remarks about the need for "LIBS=-ldl" in [netCDF >>>> #AWC-509858], so added that env setting to my build >>>> * Reproduced the 4.2.1.1/HDF 1.8.16 build with the "LIBS=-ldl" setting >>>> * NETCDF 4.3.3.1 build modified with "LIBS=-ldl" still yields the >>>> configure failure >>>> >>>> >>>> I am attaching four files as follows: >>>> >>>> 1. Build_4.2.1.1.log - stdout/err for configure and build of NETCDF >>>> 4.2.1.1 w/HDF5 1.8.16 (successful) >>>> 2. Config_4.2.1.1.log - configure.log associated with the build of >> 4.2.1.1 >>>> 3. Build_4.3.3.1.log - stdout/err for configure of NETCDF 4.3.3.1 >>>> w/HDF5 1.8.16 (failed) >>>> 4. Config_4.3.3.1.log - configure.log associated with attempted build >>>> 4.3.3.1 >>>> >>>> >>>> Assistance of a prompt nature would be greatly appreciated.... >>>> >>>> -jrm >>>> >>>> James Mason >>>> Exa Corp >>>> Burlington, MA >>>> >>>> >>>> >>> Ticket Details >>> =================== >>> Ticket ID: AWC-509858 >>> Department: Support netCDF >>> Priority: Normal >>> Status: Closed >> >> >> >> Ticket Details >> =================== >> Ticket ID: AWC-509858 >> Department: Support netCDF >> Priority: Normal >> Status: Open >> Link: >> https://andy.unidata.ucar.edu/esupport/staff/index.php?_m=tickets&_a=viewticket&ticketid=22078 >> > > > Ticket Details > =================== > Ticket ID: AWC-509858 > Department: Support netCDF > Priority: Normal > Status: Open > Link: > https://andy.unidata.ucar.edu/esupport/staff/index.php?_m=tickets&_a=viewticket&ticketid=22078 Ticket Details =================== Ticket ID: AWC-509858 Department: Support netCDF Priority: Normal Status: Open