Bug#575259: mpi-default-dev doesn't ensure that the right implementation is used
paumard at users.sourceforge.net
Wed Mar 24 15:20:09 UTC 2010
As discussed on debian-science, the way mpi-default-dev works does
that the right MPI implementation is used. For instance, if libmpich2-
installed on the system, it will _always_ be used by default because
it has the
same priority as OpenMPI and sorts before OpenMPI in lexicological
Several solutions were discussed. The easiest and most robust is to
with all the non-default implementations of mpi-dev. A smoother
solution is to
provide links like "mpicc.default" pointing to the right
install them as alternatives for mpicc et al. with a high priority.
always work on buildds but leaves a possibility to build with the wrong
implementation on a box where the admin has set the alternative
I provide a patch implementing the first of these two solutions.
Best regards, Thibaut.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mpi-default-dev depends on:
ii libopenmpi-dev 1.4.1-2 high performance message
mpi-default-dev recommends no packages.
mpi-default-dev suggests no packages.
-- debconf-show failed
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 2150 bytes
Desc: not available
More information about the debian-science-maintainers