23 Apr
2011
23 Apr
'11
11:53 a.m.
On Sat, Apr 23, 2011 at 18:45, Barry Smith <[email protected]> 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.