Matthew Knepley <[email protected]> writes: > The other packages just break. We put it in to interact with Python, > which requires an MPI shared library.
Huh? We're building PETSc, which does not depend on Python (except for configure). Why should PETSc configure be deciding how to make the library work with some Python that may never exist? I must not understand what you're trying to say. > 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.
pgpE_A0bS9fbj.pgp
Description: PGP signature
