[petsc-users] Open MPI library version error

[Satish Balay]

Or disable this check.. i.e change

#elif defined(OMPI_MAJOR_VERSION)
to
#elif defined(OMPI_MAJOR_VERSION_disable_check)

Satish

On Tue, 11 May 2021, Matthew Knepley wrote:

> On Tue, May 11, 2021 at 5:34 AM Daniel Stone <daniel.stone at opengosim.com>
> wrote:
> 
> > Hi Pierre,
> >
> > I'm using 3.12.2, which is a bit old, but needed for the Pflotran version
> > I'm using. It certainly predates that merge.
> >
> > Many thanks for pointing me to that merge - if nothing else I could now
> > study that and try manually implementing
> > it to see if it helps my situation.
> >
> 
> You might just be able to
> 
> cd $PETSC_DIR
> git cherry-pick 16dc8964ca763700383c940ec0bdd667c5da14cf
> make
> 
>   Thanks,
> 
>      Matt
> 
> 
> > Thanks,
> >
> > Daniel
> >
> > On Tue, May 11, 2021 at 10:28 AM Pierre Jolivet <pierre at joliv.et> wrote:
> >
> >> Hello Daniel,
> >> Which PETSc version are you using?
> >> I think this has been addressed there:
> >> https://gitlab.com/petsc/petsc/-/merge_requests/3671
> >>
> >> Thanks,
> >> Pierre
> >>
> >> On 11 May 2021, at 11:22 AM, Daniel Stone <daniel.stone at opengosim.com>
> >> wrote:
> >>
> >> Hello,
> >>
> >> I have the following error:
> >>
> >> PETSc Error --- Open MPI library version
> >> FUJITSU MPI Library 4.0.0 (4.0.1fj4.0.0) does not match what PETSc was
> >> compiled with 4.0, aborting
> >>
> >> I have to configure and compile petsc in a cross compilation environment
> >> and run it
> >> in a different one. I'm trying to run src/snes/examples/tutorials/ex19 to
> >> confirm things
> >> are working.
> >>
> >> It looks like this error could be down to some confusion with string
> >> comparison
> >> ("4.0.0" =/= "4.0"), or it could be some nightmare misalignment between
> >> the two
> >> environments I have to use, and/or my efforts to configure PETSc. I'm
> >> trying to
> >> determine which.
> >>
> >> Is there some way to turn off this version checking, to see if it is just
> >> a string comparison
> >> error and maybe the rest of the program will run fine? Or could someone
> >> point me to where
> >> in the source code/configuration scripts these numbers are harvested and
> >> this error is generated, so I can try to get a better idea about what is
> >> going on?
> >>
> >> Thanks,
> >>
> >> Daniel Stone
> >>
> >>
> >>
> 
>