Could you send the configure.log of your petsc build? --Junchao Zhang
On Mon, Aug 23, 2021 at 3:37 PM Mancinelli, Asher J via petsc-maint < [email protected]> wrote: > Hello all, > > We are attempting to build an application that relies on PETSc with Cray > MPICH, and we're encountering the following build-time error: > > cd <snip>/exago/build/src/utils && hipcc -DHAVE_HIP -I<snip>/exago/include > -I<snip>/exago/build > -I<snip>spack/opt/spack/cray-sles15-zen2/clang-12.0.0-rocm4.2-mpich/magma-2.6.1-l3ckgjdgsf4yhyzzb5zaibqg5u6lzgdb/include > -isystem > <snip>spack/opt/spack/cray-sles15-zen2/clang-12.0.0-rocm4.2-mpich/mumps-5.4.0-3naioareijver7s2em5sdsejh7s74kvf/include > -isystem <cray-mpich prefix>/include -isystem > <snip>spack/opt/spack/cray-sles15-zen2/clang-12.0.0-rocm4.2-mpich/petsc-3.14.1-bzve7phvhb7sf6ikzmm3jwgzjwgnm4ro/include > -O3 -DNDEBUG -fPIC -D__INSDIR__=\"\" -std=gnu++11 -MD -MT > src/utils/CMakeFiles/UTILS_obj_static.dir/utils.cpp.o -MF > CMakeFiles/UTILS_obj_static.dir/utils.cpp.o.d -o > CMakeFiles/UTILS_obj_static.dir/utils.cpp.o -c > <snip>/exago/src/utils/utils.cpp > In file included from <snip>/exago/src/utils/utils.cpp:2: > In file included from <snip>/exago/include/common.h:8: > In file included from > <snip>/spack/opt/spack/cray-sles15-zen2/clang-12.0.0-rocm4.2-mpich/petsc-3.14.1-bzve7phvhb7sf6ikzmm3jwgzjwgnm4ro/include/petsc.h:5: > In file included from > <snip>/spack/opt/spack/cray-sles15-zen2/clang-12.0.0-rocm4.2-mpich/petsc-3.14.1-bzve7phvhb7sf6ikzmm3jwgzjwgnm4ro/include/petscbag.h:4: > <snip>/spack/opt/spack/cray-sles15-zen2/clang-12.0.0-rocm4.2-mpich/petsc-3.14.1-bzve7phvhb7sf6ikzmm3jwgzjwgnm4ro/include/petscsys.h:211:6: > error: "PETSc was configured with MPICH but now appears to be compiling > using a non-MPICH mpi.h" > # error "PETSc was configured with MPICH but now appears to be > compiling using a non-MPICH mpi.h" > ^ > > I've replaced some possibly sensitive paths with text in angle brackets > for a description, eg <cray-mpich prefix>. > > Is this a known issue? Is it apparent from this text that we're doing > anything wrong? > > Our source may be found at this repository: > https://gitlab.pnnl.gov/exasgd/frameworks/exago. > <https://gitlab.pnnl.gov/exasgd/frameworks/exago> > ExaSGD / Frameworks / ExaGO ยท GitLab > <https://gitlab.pnnl.gov/exasgd/frameworks/exago> > PNNL GitLab - Scientific Software Collaboration Platform > gitlab.pnnl.gov > > > Cheers, > > *Asher Mancinelli* > > Research Computing > > *Pacific Northwest National Laboratory* > > >
