libvtkhdf5 contains unmangled symbols
When I build paraview with HDF5 coming from VTK/ThirdParty/hdf5, the resulting libvtkhdf5-pv10.so contains many unmangled symbols starting with H5. For example H5D_def_layout_chunk_g
, which I also find in a build-from-vanilla-source libhdf5.so shared library.
I thought the idea was that no symbol clashes between a loaded vanilla libhdf5 and the libvtkhdf5 shared libraries could occur, thereby enabling another code to have libhdf5 loaded, and also load libvtkhdf5 (maybe as part of in-situ processing) and not have symbols clashing, leading to unpredictable behavior, especially when the two libraries have different versions.
For reference, find attached the results of
nm libvtkhdf5-pv5.10.so | grep \ vtkhdf5 > libvtkhdf5-mangled.txt
and nm libvtkhdf5-pv5.10.so | grep \ H5 > libvtkhdf5-unmangled.txt
Maybe I'm going about this the wrong way, and this is not a problem.
@utkarsh.ayachit I hope it is OK if I assign this to you, I saw some MR's that also related to symbol mangling of HDF5 with your name on it.