On Tue, Apr 25, 2017 at 3:42 PM, Barry Smith <bsm...@mcs.anl.gov> wrote:
> > The error message is generated based on the macro MPICH_NUMVERSION > contained in the mpi.h file. > > Apparently MVAPICH also provides this macro, hence PETSc has no way to > know that it is not MPICH. > > If you can locate in the MVAPICH mpi.h include files macros related > explicitly to MVAPICH then we could possibly use that macro to provide a > more specific error message. > There is also a macro: MVAPICH2_NUMVERSION in mpi.h. We might use it to have a right message. Looks possible for me. Fande, > > Barry > > > > On Apr 25, 2017, at 4:35 PM, Kong, Fande <fande.k...@inl.gov> wrote: > > > > Hi, > > > > We configured PETSc with a version of MVAPICH, and complied with another > version of MVAPICH. Got the error messages: > > > > error "PETSc was configured with one MPICH mpi.h version but now appears > to be compiling using a different MPICH mpi.h version" > > > > > > Why we could not say something about "MVAPICH" (not "MPICH")? > > > > Do we just simply consider all MPI implementations (MVAPICH, maybe Intel > MPI, IBM mpi?) based on MPICH as "MPICH"? > > > > Fande, > >
