-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tests fail to build: mpi library not linked #47
Comments
Hi @drew-parsons. Let me ask on #39. |
Hi @weslleyspereira Sorry, I overlooked the C compiler line being reset to the MPI wrapper. That can be commented too to make it consistent with commit #61c60f5 and update the test configuration as @drew-parsons suggested. I think the fix here is to simply add |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For the new v2.2.0, the handling of the fortran compiler was changed in commit #61c60f5 to keep the identity of the fortran compiler (
CMAKE_Fortran_COMPILER
) separate from the MPI fortran compiler (MPI_Fortran_COMPILER
). Previously the mpi wrapper was also used as the plain fortran compiler.That change makes sense. The serial and mpi variants of the fortran compiler should be handled separately. But it has a consequence on the tests in TESTING. These tests link against
-lscalapack
, but libscalapack requires libmpi. It's not automatically pulled in, the-lmpi
need to be added when compiling the tests.The tests are currently configured to use the standard compiler (implicitly, CMAKE_Fortran_COMPILER). Before commit #61c60f5, the identification with MPI_Fortran_COMPILER meant that mpifort added the required
-lmpi
. Now that CMAKE_Fortran_COMPILER is kept separate, gfortran is used without-lmpi
, so tests fail to link, giving errors like (in the case of xclu from TESTING/LIN)I guess the test configuration should be updated so that the tests get compiled using
MPI_Fortran_COMPILER
The text was updated successfully, but these errors were encountered: