On Tue, Dec 11, 2012 at 7:55 PM, Drew Parsons wrote: > > I've got the full build log now. It just confirms that hdf5 was not > found and therefore not built against: > > checking hdf5.h usability... no > checking hdf5.h presence... no > checking for hdf5.h... no > configure: WARNING: HDF5 library not found. Octave will not be able to > save or load HDF5 data files. > > It is weird, since libhdf5-openmpi-dev is installed and does supply > hdf5.h: > $ ls -l /usr/include/hdf5.h > -rw-r--r-- 1 root root 2655 Mar 8 2012 /usr/include/hdf5.h > > I guess that's another reproducibility test: if you have > libhdf5-openmpi-dev installed, do you get > "checking hdf5.h usability... yes" ?
Yes, if I add --with-hdf5-includedir=/usr/include/mpi. If not I get the same "HDF5 library not found." > I did reinstall libhdf5-openmpi-dev and libhdf5-openmpi-7 to make sure > it wasn't just a corrupted installation. > > So that's two octave-hdf questions: > > 1) why is libhdf5-openmpi-7 now making octave crash on my system (when > it doesn't affect yours) ? Or is it any hdf5 variant? Have you tried installing the non-openmpi libhdf5-7 with the original octave packages to see if that also crashes on you? I didn't see whether you had tried that yet. > 2) why does my local build not recognise the hdf5.h provided by > libhdf5-openmpi-dev? Answered above. Basically because hdf5 does not use pkg-config and its public header files have dependencies on the mpi headers. -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
