# Error in Paraview 5.8.1 - Could not find the MPI external dependency.
**URL:** https://discourse.paraview.org/t/error-in-paraview-5-8-1-could-not-find-the-mpi-external-dependency/6306
**Category:** ParaView Support
**Created:** [January 26, 2021, 6:40pm UTC](https://discourse.paraview.org/t/error-in-paraview-5-8-1-could-not-find-the-mpi-external-dependency/6306 "2021-01-26T18:40:19Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@kmilo9999](https://discourse.paraview.org/u/kmilo9999)
#### Post date: [January 26, 2021, 6:40pm UTC](https://discourse.paraview.org/t/error-in-paraview-5-8-1-could-not-find-the-mpi-external-dependency/6306/1 "2021-01-26T18:40:19Z")
Hello,
I am trying to build paraview 5.8.1 from the source code, and I am enabling MPI. However I am getting the error:
```
CMake Error at VTK/CMake/vtkModule.cmake:4112 (message):
Could not find the MPI external dependency.
Call Stack (most recent call first):
VTK/CMake/vtkModule.cmake:4635 (vtk_module_find_package)
VTK/Utilities/MPI/CMakeLists.txt:1 (vtk_module_third_party_external)
```
1. It does build without MPI
2. I am using openmpi\_4.0.5\_intel\_2020.2
3. when I compile with openmpi\_4.0.1 it does build, compile and install.
Any thoughts ?
I appreciate the help in advance.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [January 26, 2021, 8:51pm UTC](https://discourse.paraview.org/t/error-in-paraview-5-8-1-could-not-find-the-mpi-external-dependency/6306/2 "2021-01-26T20:51:01Z")
What version of CMake are you using. Does 5.9/master work at all (trying to figure out whether FindMPI is at fault or not)? We might need to update FindMPI for this release/build of OpenMPI.
Cc: @chuckatkins
---
### Author:  [@kmilo9999](https://discourse.paraview.org/u/kmilo9999)
#### Post date: [January 26, 2021, 8:59pm UTC](https://discourse.paraview.org/t/error-in-paraview-5-8-1-could-not-find-the-mpi-external-dependency/6306/3 "2021-01-26T20:59:43Z")
I am using cmake 3.15.4.
I can’t tests paraview 5.9 because it requires qt.12 which is not installed in the system.
Any suggestions ?
---
### Author:  [@kmilo9999](https://discourse.paraview.org/u/kmilo9999)
#### Post date: [January 27, 2021, 12:17pm UTC](https://discourse.paraview.org/t/error-in-paraview-5-8-1-could-not-find-the-mpi-external-dependency/6306/4 "2021-01-27T12:17:54Z")
Hello again,
I managed to install qt 5.12 and paraview 5.9 using openmpi\_4.0.5\_intel\_2020.2. In the cmake configuration I used :
-DCMAKE\_C\_COMPILER=/gpfs/runtime/opt/mpi/openmpi\_4.0.5\_intel\_2020.2/bin/mpicc -DCMAKE\_CXX\_COMPILER=/gpfs/runtime/opt/mpi/openmpi\_4.0.5\_intel\_2020.2/bin/mpicx
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [January 27, 2021, 4:02pm UTC](https://discourse.paraview.org/t/error-in-paraview-5-8-1-could-not-find-the-mpi-external-dependency/6306/5 "2021-01-27T16:02:50Z")
Seems that 5.8.1’s FindMPI that it ships with is insufficient for that OpenMPI. I suspect using a newer CMake might also help, but I can’t guarantee anything.
---
### Author:  [@olesenm](https://discourse.paraview.org/u/olesenm)
#### Post date: [January 27, 2021, 5:36pm UTC](https://discourse.paraview.org/t/error-in-paraview-5-8-1-could-not-find-the-mpi-external-dependency/6306/6 "2021-01-27T17:36:22Z")
Not related to this message that I always keep seeing?
It looks like the regular find mpi tries various C, CXX etc languages and then the next package warns about the syntax.
```auto
CMake Warning (dev) at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:272 (message):
The package name passed to `find_package_handle_standard_args` (MPI_C) does
not match the name of the calling package (MPI). This can lead to problems
in calling code that expects `find_package` result variables (e.g.,
`_FOUND`) to follow a certain pattern.
```
---
### Author:  [@olesenm](https://discourse.paraview.org/u/olesenm)
#### Post date: [January 27, 2021, 5:46pm UTC](https://discourse.paraview.org/t/error-in-paraview-5-8-1-could-not-find-the-mpi-external-dependency/6306/7 "2021-01-27T17:46:37Z")
I have mpich, openmpi and openmpi2 installed on my suse system:
- /usr/lib64/mpi/gcc/mpich
- /usr/lib64/mpi/gcc/openmpi
- /usr/lib64/mpi/gcc/openmpi2
Currently active is openmpi2 (`mpicc is /usr/lib64/mpi/gcc/openmpi2/bin/mpicc`)
but it finds mpich instead.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [January 27, 2021, 5:58pm UTC](https://discourse.paraview.org/t/error-in-paraview-5-8-1-could-not-find-the-mpi-external-dependency/6306/8 "2021-01-27T17:58:44Z")
That warning can be ignored; newer FindMPI versions have fixed the problem; it’s just a warning that something _might_ be wrong (FindMPI is doing that part right at least).
As for OpenSuse things…FindMPI is really complicated. You can try setting some of the cache variables that are mpich-y to being the openmpi ones.
---
### Author:  [@olesenm](https://discourse.paraview.org/u/olesenm)
#### Post date: [January 27, 2021, 7:33pm UTC](https://discourse.paraview.org/t/error-in-paraview-5-8-1-could-not-find-the-mpi-external-dependency/6306/9 "2021-01-27T19:33:12Z")
Setting `MPI_HOME` as a hint seems to help guide things.