[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

hdf5

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.

  • Subject: hdf5
  • Date: Mon, 15 Jan 2018 19:11:23 +0000

Before I spend too much time going in the wrong direction :-$, is there a simple way to get around this (other than disabling the error message *ALIEN*).. I use several applications that use netcdf / hdf5, and it seems all package members rarely agree on which version they wish to use! (I'm not trying to say anything, just trying to stably get around the error without future issue 8-))

for example:
/data/GOES16/EFD/Channel13/20180115$ 
Warning! ***HDF5 library version mismatched error***
The HDF5 header files used to compile this application do not match
the version used by the HDF5 library to which this application is linked.
Data corruption or segmentation faults may occur if the application continues.
This can happen when an application was compiled by one version of HDF5 but
linked with a different version of static or shared HDF5 library.
You should recompile the application or check your shared library related
settings such as 'LD_LIBRARY_PATH'.
You can, at your own risk, disable this warning by setting the environment
variable 'HDF5_DISABLE_VERSION_CHECK' to a value of '1'.
Setting it to 2 or higher will suppress the warning messages totally.
Headers are 1.8.18, library is 1.8.20


cheers,

--patrick