[petsc-dev] Errors from PETSc 3.11 and 3.12 headers

[Balay, Satish]

[petsc at petsc-c7 petsc:maint-3.11]$ gcc --version
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39)

On CentOS-7 I get:

[petsc at 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.

Satish

On Sun, 22 Dec 2019, Antonio Trande wrote:

> On 22/12/19 20:15, Balay, Satish wrote:
> > This error is strange. The issue does not come up in petsc build - but in petsc4py build.
> > 
> > I see the petsc4py build is with:
> > 
> >>>>>>>
> > + CFLAGS=' -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches   -m64 -mtune=generic'
> > 
> > mpicc -pthread -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O3 -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -DPETSC_DIR=/usr -I/usr/include/openmpi-x86_64 -I/usr/include/openmpi-x86_64/hypre -I/usr/lib64/gfortran/modules/openmpi/petsc -I/usr/include/openmpi-x86_64/petsc -I/usr/include -Isrc/include -I/usr/lib64/python3.6/site-packages/numpy/core/include -I/usr/include/python3.6m -c src/PETSc.c -o build/temp.linux-x86_64-3.6/src/PETSc.o
> > <<<
> > 
> > I've attempted a petsc+petsc4py build using both the following on fedora-31 [with petsc-3.12/maint] - and there were no errors 
> 
> Yes, it does not happen on Fedora. That error appears on CentOS-7
> machines only, both with Python2 and Python3.
> 
> petscconf.h is attached
> 
> 
>