Gilles Filippini a écrit , Le 31/08/2014 11:04: > Hi Yaroslav, > > Yaroslav Halchenko a écrit , Le 31/08/2014 02:17: >> both ants and nifti2dicom (and probably others) recent FTBFS are due to >> recentish upload of hdf5 1.8.13+docs-8 which was previously only in >> experimental after its big RF in (1.8.13+docs-1) which stopped providing >> '/usr/lib/x86_64-linux-gnu/libhdf5.so' but provides separate builds for >> each flavor: >> >> /usr/lib/x86_64-linux-gnu/hdf5/mpich/libhdf5.so libhdf5-mpich-dev [amd64] >> /usr/lib/x86_64-linux-gnu/hdf5/openmpi/libhdf5.so libhdf5-openmpi-dev >> [amd64] >> /usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5.so libhdf5-dev [amd64] >> >> Gilles, I wondered, shouldn't there still be a >> /usr/lib/x86_64-linux-gnu/libhdf*.so* managed via alternatives, e.g. like >> blas/atlas do it? > > I didn't spot ants as a rdep oh hdf5. I'll have a look. > About nifti2dicom, my previous tests reported no FTBFS after binNMUing > vtk6. I'll have a look as well.
It seems the FindITK.cmake macro reports the wrong path for hdf5 libraries. Still investigating... _g.
signature.asc
Description: OpenPGP digital signature
