Error while building Teton with GCC and Mvapich2
Nobody has claimed this yet.
- Dominant language
- Fortran
- Stars
- 8
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Hello, I am building UMT via Spack, and have run into this following error message that calls to mismatch in Teton source for MPI. Should I change my MPI version? I am using Mvapich2 downloaded from spack
(building using Spack latest, and Mvapich2 MPI, GCC 11.3)
==> Installing umt-master-ah6pibyhzhavaitbn5e5pcfo3bqc7kzc ==> No binary for umt-master-ah6pibyhzhavaitbn5e5pcfo3bqc7kzc found: installing from source ==> No patches needed for umt ==> umt: Executing phase: 'initconfig' ==> umt: Executing phase: 'cmake' ==> umt: Executing phase: 'build' ==> Error: ProcessError: Command exited with status 2: `/home/13_spack_UMT/spack/opt/spack/linux-ubuntu20.04-cascadelake/gcc-11.3.0/gmake-4.4.1-jilr5zmh37kfd4rfidm6iyq6vdws5oii/bin/make' '-j32'
24 errors found in build log:
176
177 1048 | call MPI_Irecv(recvBuf, nrecv, MPI_REAL8, irecv, &
178 | 1
179 ......
180 1126 | call MPI_Irecv(recvBuf, nrecv, MPI_INTEGER, irecv, &
181 | 2
182 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)).
183 /tmp/spack-stage/spack-stage-umt-master-ah6pibyhzhavaitbn5e5pcfo3bqc7kzc/spack-src/src/teton/misc/mpif90_mod.F90:1010:20:
184
185 1010 | call MPI_Irecv(recvBuf, nrecv, MPI_REAL8, irecv, &
186 | 1
187 ......
188 1126 | call MPI_Irecv(recvBuf, nrecv, MPI_INTEGER, irecv, &
189 | 2
All the 24 errors are along this same line in the same file
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Spack build log and src/teton/misc/mpif90_mod.F90 around lines 1010 and 1126, where the MPI_Irecv type mismatches are reported. Reproduce the UMT build with GCC 11.3 and Mvapich2, then determine whether the failure is tied to the compiler/MPI combination. Done means the build completes or the required compatible configuration is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- build-system, hpc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100