Methods to obtain (
–Download file and then run:
gzip -cd <distribution>.tar.gz | tar xzf -
chrome – Download file and then run:
Known Problems at Release Time
Several example programs in HDF5 source/java/examples will fail in “make check” when HDF5 built with Autotools has been configured with --prefix=<install directory path>. This occurs because Autotools puts the path for libhdf5.so.dylib in libhdf5_java.dylib, and the failed example programs attempt to dlopen libhdf5.so.dylib in the install location which does not yet exist. The problem does not occur when no prefix is given, and only on macOS platforms.
The simplest workaround is to run “make install” before “make check”, which will insure that libhdf5.so.dylib is found when needed by libhdf5_java.dylib. If “make install” cannot be run before “make check”, running “make -I check” after the java examples have failed will allow running any tests that did not run following the java examples. The output can then be searched to find “FAILED” for any tests that fail following the java examples.
The function prototype for H5Treclaim was mistakenly added to code for HDF5 1.10.9; however no implementation code was added. This prototype has been removed, resulting in a source incompatibility for shared library versions between HDF5 versions 1.10.10 and 1.10.9, but not binary incompatibility since the function was not implemented.
Tested Platforms and Configuration Features
NOTE: HDF5-1.10 requires MPI 3.
See the Release Notes for details.