[petsc-dev] known-mpi-shared-libraries

[Matthew Knepley]

On Fri, Jun 6, 2014 at 3:20 AM, Jed Brown <jed at jedbrown.org> wrote:

> Why can't we find a way to avoid needing this option?  I'm not aware of
> other packages with an analogous configure option.  Are they giving up
> something that we consider valuable?
>

The other packages just break. We put it in to interact with Python, which
requires
an MPI shared library. If you do not check, the executable just breaks in
weird ways,
like it would for PyTrilinos. The check is an actual check, but it requires
running.

   Matt


> Satish Balay <balay at mcs.anl.gov> writes:
>
> > run configure with the addtional option --known-mpi-shared-libraries=1
>



-- 
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/20140606/08c4caa5/attachment.html>