On Thu, 2005-09-08 at 18:28 -0400, Faheem Mitha wrote:
> 
> 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.

Okay, I'll do so when I have a package ready.

Thanks,

-Adam
-- 
GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Welcome to the best software in the world today cafe!
http://www.take6.com/albums/greatesthits.html


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to