Drew Parsons a écrit le 05/04/2020 à 15:28 : > On 2020-04-05 20:38, Gilles Filippini wrote: >>> >>> But it must be something else from these new h5py upstream patches >>> that's leading to any other bitshuffle errors (the ones apart from the >>> file-not-found error). >> >> Nope. Seems related to the h5py 'serial' flavour only. It appears for >> the first time when you configure the build for both flavours. If I >> force the 'mpi' flavour installation *without* the 'serial' one, >> bitshuffle builds fine. >> > > A good clue. I've pushed a h5py without the patches, but looks like the > problem might remain. Strange if bitshuffle builds fine against h5py-mpi > but not against h5py-serial. You'd expect any problem to come the other > way around.
I suspect a mismatch between mpi and serial build-depdencies: python3-h5py-serial + libhdf5-dev => OK python3-h5py-serial + libhdf5-openmpi-dev => KO python3-h5py-mpi + libhdf5-dev => KO python3-h5py-mpi + libhdf5-openmpi-dev => KO(*) (*) because it fails to import h5py submodules when python3-h5py-serial is not installed: ImportError: cannot import name 'h5f' from 'h5py' (unknown location) With the 2.10.0-5 layout it seems impossible to build against the 'mpi' flavour, while building against 'serial' flavour requires serial flavour of libhdf5 -dev package as well. _g.
signature.asc
Description: OpenPGP digital signature