Hi Drew,
Drew Parsons a écrit le 15/11/2022 à 16:28 :
h5py is building fine against the shared libraries with
HDF5_USE_SHLIB=yes, but leaves a question about rpath.
Notice that `h5pcc --showconfig -shlib` includes
"-L/usr/lib/x86_64-linux-gnu/hdf5/openmpi -lhdf5_hl -lhdf5 -Wl,-rpath
-Wl,/usr/lib/x86_64-linux-gnu/hdf5/openmpi"
The h5py python extensions get linked with this, such the h5py .so files
are generated with
NEEDED libhdf5_openmpi.so.103
RUNPATH /usr/lib/x86_64-linux-gnu/hdf5/openmpi
In normal package policy we try to remove RUNPATH, and in the case of
the hdf5 libraries libhdf5_openmpi.so.103 is available in the standard
library path at /usr/lib/x86_64-linux-gnu/. In fact
libhdf5_openmpi.so.103 is not even found in
/usr/lib/x86_64-linux-gnu/hdf5/openmpi (instead libhdf5.so is found
there as a symlink to ../../libhdf5_openmpi.so).
As far as I can tell, the -rpath entry in the h5pcc configuration is
redundant, possibly even wrong (since the linked library is
libhdf5_openmpi.so.103, not the more general libhdf5.so)
Should rpath be removed from the h5pcc shlib configuration?
I've just uploaded hdf5 1.10.8+repack-2 which should fix this issue.
Best,
_g.
