[petsc-maint #38919] Re: stupid, stupid, stupid MPI.py

[Matthew Knepley]

On Mon, Dec 14, 2009 at 10:39 AM, Lisandro Dalcín <dalcinl at gmail.com> wrote:

> On Mon, Dec 14, 2009 at 1:33 PM, Matthew Knepley <knepley at gmail.com>
> wrote:
> > On Mon, Dec 14, 2009 at 10:28 AM, Lisandro Dalcín <dalcinl at gmail.com>
> wrote:
> >>
> >> On Mon, Dec 14, 2009 at 11:34 AM, Matthew Knepley <knepley at gmail.com>
> >> wrote:
> >> >
> >> > If we are using shared libraries, and the MPI shared library was
> broken,
> >> > the
> >> > configure failed. This option was added
> >> > to allow the user to turn off that check.
> >> >
> >>
> >> What does 'broken' means? How can the lib be broken for configure, but
> >> not for linking PETSc or user programs?
> >
> > It would also be broken there too, and fall back to the static libraries.
> >
>
> Sorry, I'm still confused. What does 'broken' means? Sorry about my
> ignorance: In the case of a corrupted (whatever that could mean)
> shared lib file, does the linker fall back to use a static lib?
>

I believe so. I know that is why I put this in. The shared lib test would
break, since
they were not functional, but the library overall would work.

  Matt


> --
> Lisandro Dalcín
> ---------------
> 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
lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20091214/d695aeb8/attachment.html>