On 2/7/20 11:43 PM, vachan potluri wrote:
I really appreciate and value your involvement in this thread. I have
attached mpi.h with this mail. I want to mention that I added this line
in FindMPI.cmake just before DEAL_II_FIND_FILE(MPI_MPI_H ...):
MESSAGE(STATUS "Searching for mpi.h in ${MPI_CXX
Vachan,
I saw on the other thread that you were using CMake 3.5. I would advise to
download a newer version of CMake. deal.II uses FindMPI from CMake and this
was rewritten in CMake 3.10 to fix problems with Cray supercomputers.
Best,
Bruno
On Saturday, February 8, 2020 at 1:43:59 AM UTC-5,
Dear Prof. Bangerth,
Can you attach it to a reply? It would be interesting to see why the
> version
> detection didn't work. (Although I see that cmake complains that it can't
> find
> the file, so that is probably the issue. I don't know why it can't find
> the
> file...)
I really apprecia
The MPI version is 3.1. But will this be of use? After all, the include paths,
linker flags and library variables will still be blank.
It's still possible that everything links correctly. What happens if you run
cmake and then compile? Does it work?
In the best of all worlds, everything co
>
> If you know to which standard the MPI installation is conforming, you
> could try to set it via
> cmake -DMPI_VERSION=...
> yourself.
The MPI version is 3.1. But will this be of use? After all, the include
paths, linker flags and library variables will still be blank.
But separately, we
