Oliver Sander a écrit , Le 16/01/2014 14:30:
I had a quick look at the package, since the hdf5 FAQ says:
"If the build completes properly and the tests pass, then the installation should be 

You need two options for 'configure': --enable-unsupported and --enable-cxx.
Somewhat surprisingly, the first one is already set in debian/rules.
I added --enable-cxx and tried to build the package on my Debian Jessie machine.

The build fails with

make[2]: Entering directory 
Making all in src
make[3]: Entering directory 
   CXX      H5Exception.lo
In file included from ../../../../src/hdf5.h:24:0,
                  from ../../../../c++/src/H5Include.h:17,
                  from ../../../../c++/src/H5Exception.cpp:18:
../../../../src/H5public.h:63:20: fatal error: mpi.h: No such file or directory
  #   include <mpi.h>
compilation terminated.
make[3]: *** [H5Exception.lo] Fehler 1
make[3]: Leaving directory 
make[2]: *** [all-recursive] Fehler 1
make[2]: Leaving directory 
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/home/sander/hdf5/hdf5-1.8.12/debian/build-openmpi'
make: *** [build-stamp-openmpi] Fehler 2
dpkg-buildpackage: Fehler: Fehler-Exitstatus von debian/rules build war 2

Any ideas?


IMHO the only right solution would be to have the three flavors of the library (serial, openmpi, mpich) co-installable, instead of playing with workarounds unsupported upstream.

But we have yet to find out how to achieve this goal :(

I've just had a look at fedora where the libs are co-installable. They use rpath for the MPI flavors. I don't like this solution which is acceptable for private libraries only.

Any other idea?



Pkg-grass-devel mailing list

Reply via email to