dolfin team mailing list archive

[Faheem Mitha <faheem@xxxxxxxxxxxxx>]

On Thu, 8 Sep 2005, Adam C Powell IV wrote:

> Hello,
>
> MPICH and LAM are *not* binary compatible, so it's not possible to
> configure their links at runtime.  That's why PETSc links specifically
> to the mpich libraries.  It is not possible to use the alternatives
> system to switch between them.
>
> But you can configure PETSc to use lam.  The details on how to do this
> are in the README.Debian file which comes with libpetsc2.2.0-dev.

You should tell all this to the DOLFIN developers. I don't understand 
these issues that well, and am not in a position to change things (if 
necessary) anyway.

> How that will work with 2.3.0 will depend on how I package it.  I'm
> afraid I'm stuck now on getting hypre to build at all with the new
> toolchain, spent about eight hours on it yesterday. :-(  When all of the
> new mpich dependencies get into testing, then I'll focus on petsc again.

Ok. I think that a little communication up front with the DOLFIN 
developers would be beneficial to make sure the Debian DOLFIN package is 
compatable with the Debian PETSc package. If you could send me a preview 
of the Debian PETSc 2.3 package when it is available, I'll try to get 
DOLFIN to build against it.

Thanks.                                                          Faheem.