[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: updating mpi-defaults (decommissioning lam)

On 10/05/11 at 20:16 -0700, Nicholas Breen wrote:
> On Thu, Apr 07, 2011 at 02:58:42PM +1000, Drew Parsons wrote:
> > mpi-defaults current makes a number of architectures broken [1] because
> > they have the default mpi implementation set to lam (where openmpi is
> > not available)
> > 
> > A patch changing the default mpi from lam to mpich has been stagnating
> > in git for more than a year, and missed the release of squeeze.
> > 
> > I have the will to upload the new mpi-defaults (I'll apply the patch in
> > #575259 while I'm at it) and would like to do so.  Please speak up if
> > you would prefer me not to take this action.
> Let's do it.  I believe the list of remaining issues [1] before we can start
> removing LAM and MPICH1 entirely is quite small.  There are two categories:
> first, the build failures that Lucas Nussbaum identified last year [2] caused
> by including mpich2 in mpi-default-dev:
> On Wed, Mar 17, 2010 at 08:33:40AM +0100, Lucas Nussbaum wrote:
> > The following 11 packages failed to build:
> > apbs looks for mpi.h in the wrong place
> > petsc Nonexistent directory: /usr/lib/mpich2 for key with-mpi-dir (?)
> Both of these expect /usr/lib/mpich2/{include,lib} to exist.  The other three
> MPI implementations all have such directories, either as the actual location of
> the corresponding files or symlinks to them.  MPICH2 maintainers: would you
> consider adding these directories as well?

Yes. Could you file a bug and/or provide a patch?

I am a bit busy with other Debian tasks currently, so, while I'm willing
to do the necessary uploads of mpich2 for this transition, I can't
commit to doing more work myself.


Reply to: