[petsc-dev] forget about libmpiuni completely

Matthew Knepley knepley at gmail.com
Wed Feb 17 16:48:31 CST 2010

On Wed, Feb 17, 2010 at 2:44 PM, Lisandro Dalcin <dalcinl at gmail.com> wrote:

> On 17 February 2010 12:00, Matthew Knepley <knepley at gmail.com> wrote:
> > I am for a separate mpiuni that get downloaded. I think this makes more
> > sense with
> > our other packages concepts, and is more modular. We can reuse so much
> more
> > of
> > configure as well.
> I still fail to see the pros of having a separate mpiuni.
> I think you have to put on user's side when taking a decision about
> this. Are FINAL USERS going to have any benefits for having mpiuni as
> a separate download and having to pass a separate library in when
> invoking the  linker? If a user wants no-MPI, Is there any other

They do not pass anything. The beauty of the Petsc build.

> fake-mpi alternative supported in PETSc? If the answer is no, so then
> why bother people with a separate download?

They do not even have to download it. They specify the same option as
>From a user perspective, it does not change. From a Petsc and library
it is better.


> --
> Lisandro Dalcin
> ---------------
> Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
> Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
> Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
> PTLC - Güemes 3450, (3000) Santa Fe, Argentina
> Tel/Fax: +54-(0)342-451.1594

What most experimenters take for granted before they begin their experiments
is infinitely more interesting than any results to which their experiments
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100217/bd378206/attachment.html>

More information about the petsc-dev mailing list