[petsc-dev] detecting inappropriate mpi.h?

[Jed Brown]

On Sat, Apr 23, 2011 at 18:45, Barry Smith <bsmith at mcs.anl.gov> wrote:

> Is there any way ./configure can detect an inappropriate mpi.h (like
> /usr/include/mpi.h) in the search path and warning the user? Even something
> as crude as ls in those locations?


I want to use that mpi.h when I configure --with-mpi-dir=/usr. It's tricky
to reproduce the compiler's "system paths" so it's not clear how to portably
determine which mpi.h the compiler is going to pull in.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110423/4107b496/attachment.html>