[petsc-dev] Why does configure need 30 minutes to remind me about --known-mpi-shared-libraries?

[Aron Ahmadia]

This would substantially improve our user experience with PETSc.  Is MPI
consistently tested before other external packages?

A


On Fri, Apr 4, 2014 at 1:15 PM, Jed Brown <jed at jedbrown.org> wrote:

>
> *******************************************************************************
>          UNABLE to CONFIGURE with GIVEN OPTIONS    (see configure.log for
> details):
>
> -------------------------------------------------------------------------------
> Must give a default value for known-mpi-shared-libraries since executables
> cannot be run
>
> *******************************************************************************
>
>
> Matt, is there something consistent and maintainable that we could do so
> that all the checks for issues like this run immediately, before
> compilation tests, so that users can get error messages in a reasonable
> amount of time?  Few things are more frustrating than waiting so long to
> get a trivial error message, then start the entire process over again.
>
> And/or, what about caching results so that re-running after adding this
> flag would be fast?  (It scares me too, but I consider configure time to
> be a major usability issue.)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20140404/84c732d5/attachment.html>