Ok - you'll have to somehow make sure the same version of gcc gets used when building petsc4py
Since petsc4py is using mpicc - I think you just need to make sure the correct gcc is in PATH. Perhaps Lisandro can correct me [if there a more suitable way of specifying the correct gcc to python distutils via mpicc] Satish On Sun, 22 Dec 2019, Antonio Trande wrote: > > On 22/12/19 21:07, Balay, Satish wrote: > > [petsc@petsc-c7 petsc:maint-3.11]$ gcc --version > > gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39) > > I'm using GCC from devtools-8 packages (GCC-8.3.1) > > > > > On CentOS-7 I get: > > > > [petsc@petsc-c7 petsc:maint-3.11]$ grep PETSC_DEPRECATED_ENUM > > arch-linux2-c-debug/include/petscconf.h > > #ifndef PETSC_DEPRECATED_ENUM > > #define PETSC_DEPRECATED_ENUM(why) > > > > However - you have [in petscconf.h provided]: > > > > #ifndef PETSC_DEPRECATED > > #define PETSC_DEPRECATED(why) __attribute((deprecated)) > > #endif > > > > Is PETSc built with a different version of compiler? configure.log will > > have the details. > > > > Attached 2 logs of Configure: with and without MPI activated. > >
