On Mon, 2012-12-10 at 18:41 -0500, Mike Miller wrote: > On Mon, Dec 10, 2012 at 5:55 AM, Drew Parsons wrote: > > I presume this libhdf5 dependency is the cause of the bug, which means > > you should be able to reproduce it by replacing libhdf5-7 with > > libhdf5-openmpi-7. > > Not here, I am unable to reproduce on amd64 with libhdf5-openmpi-7 > installed and libhdf5-7 purged. I can switch between the two hdf5 > variants and Octave starts properly either way.
Hmm, still a tricky bug then :( > Can you verify that your locally built package, the one that does not > panic, did indeed link in libhdf5-openmpi-7? E.g.: > > $ ldd /usr/lib/x86_64-linux-gnu/liboctinterp.so.1 | grep hdf > libhdf5.so.7 => /usr/lib/libhdf5.so.7 (0x00007fba005f2000) > $ /usr/bin/octave --quiet --eval "octave_config_info HDF5_LIBS" > ans = -lhdf5 No, quite on the contrary. My local build apparently did not recognise libhdf5-openmpi-dev, and went ahead to build without any libhdf5 (I apologise, I didn't record the build log, perhaps I should run it again). Drew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
