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? -- 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
