NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTE: The netcdf-hdf mailing list is no longer active. The list archives are made available for historical reasons.
Quincey Koziol <koziol@xxxxxxxxxxxxx> writes: >> This problem is removed if I distribute HDF5 with netCDF, because of >> course then I could distribute a HDF5 version that I know to work with >> netCDF-4. > > Well, autoconf allows you to test for certain function's presence in a > dependent library, so you could use that feature to make certain that you > had a compatible HDF5 installation. Yes, I do this now. But it doesn't help the poor user to have my configuration just crap out. It needs to solve the problem, not just detect it. Ed -- Ed Hartnett -- ed@xxxxxxxxxxxxxxxx
netcdf-hdf archives: