HDF5's plugin loader walks every library in HDF5_PLUGIN_PATH searching for symbols of the plugin it is expecting. Currently hdf5-blosc installs it's plugin inside the prefix.lib directory. When this gets combined into a view it can be installed next to hundreds of dynamic libraries. This leads to nasty runtime errors since hdf5's own libraries are also installed here.
Proposed fix is to install plugins in a dedicated prefix.lib.hdf5_plugins directory to isolate the consequences of hdf5's plugin-loader design.
HDF5's plugin loader walks every library in
HDF5_PLUGIN_PATHsearching for symbols of the plugin it is expecting. Currentlyhdf5-bloscinstalls it's plugin inside theprefix.libdirectory. When this gets combined into a view it can be installed next to hundreds of dynamic libraries. This leads to nasty runtime errors since hdf5's own libraries are also installed here.Proposed fix is to install plugins in a dedicated
prefix.lib.hdf5_pluginsdirectory to isolate the consequences of hdf5's plugin-loader design.