When building ParaView 5.7.0-RC1 with cmake 3.11.4,
I have found that the FindMPI module is not properly
finding the MPI version on our Centennial super-computer.
Is there a recommended version of cmake to use
with ParaView 5.7.0-RC1? ParaView 5.6.1 did not have
an issue with FindMPI and cmake 3.11.4.
The MPI module I am using on Centennial is mpi/sgimpt/2.15
The gcc compiler module I am using is compiler/gcc/6.1.0
and the error’s that the superbuild is returning are (when
the superbuild attempts to configure ParaView 5.7.0-RC1 itself)
– Could NOT find MPI_C (missing: MPI_C_WORKS)
– Could NOT find MPI (missing: MPI_C_FOUND C)
CMake Error at VTK/CMake/vtkModule.cmake:3640 (message):
Could not find the MPI external dependency.
Call Stack (most recent call first):
VTK/Cmake/vktModule.cmake:4095 (vtk_module_find_package)
VTK/Utilities/MPI/CMakeLists.txt:1 (vtk_module_third_party_external)
– Configure incomplete, errors occured!
See also “/usr/cta/DAAC/build/PV/Build_5.7.0-RC1_osmesa_test/superbuild/paraview/build/CMakeFiles/CMakeOutput.log”.
See also “/usr/cta/DAAC/build/PV/Build_5.7.0-RC1_osmesa_test/superbuild/paraview/build/CMakeFiles/CMakeError.log”.
CMake Error at /usr/cta/DAAC/build/PV/Build_5.7.0-RC1_osmesa_test/superbuild/sb-paraview-configure.cmake:47 (message):
Failed with exit code 1
Please let me know if you need any additional info.
I have found that I can modify the FindMPI.cmake module
to manually set all necessary values and hardcode the paths
to the appopriate compilers, include files and libraries, but that
is not a preferred solution as it is system and version specific,
and not a robust solution.
Agreed. Does a standalone project with find_package(MPI) work? VTK does have its own copy, so maybe it needs updated to what a newer CMake provides? If not, do we have access to this machine at all to debug/iterate on fixing it?