As you know, building against MPI is tricky. Lots of folks have
adopted a strategy of building against OpenMPI on architectures it
supports and using LAM for the rest . However, that means the
knowledge of which architectures can build OpenMPI is replicated in
the control files of many packages. I package MINC, which uses MPI
via hdf5. The current hdf5 packaging forces me to replicate this
information in the MINC control file.
Recently, Adam Powell created a meta-package  to centralize this
knowledge; c.f. discussion in . The new meta-package produces two
binary meta-packages: mpi-default-dev and mpi-default-bin which depend
on libopenmpi-dev and openmpi-bin respectively on the platforms where
they are available, and lam4-dev and lam-runtime on the others.
Please consider introducing corresponding mpi-using hdf5 packages,
either in addition to libhdf5-lam, libhdf5-mpich, etc or as a
replacement for them.
The goal would be to have libhdf5-mpi-default-dev for packages such as
MINC to build with.
-- System Information:
Debian Release: 5.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Pkg-grass-devel mailing list