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. 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. Thanks for the report, Adam On Mon, 2005-09-05 at 14:07 -0400, Faheem Mitha wrote: > Dear Adam Powell, > > I'm forwarding this message (from the DOLFIN dev mailing list) here since > this looks like it might be relevant to packaging PETSc. > > You probably understand these issues better than I do. However, feel free > to ask for clarifications if necessary. > > How is the packaging going? > > Faheem. -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]
