December 2019 - petsc-dev - mailman3.cels.anl.gov

Re: [petsc-dev] Errors from PETSc 3.11 and 3.12 headers
by Balay, Satish 22 Dec '19

22 Dec '19

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. > >

1 0

Re: [petsc-dev] Errors from PETSc 3.11 and 3.12 headers
by Antonio Trande 22 Dec '19

22 Dec '19

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. -- --- Antonio Trande Fedora Project mailto 'sagitter at fedoraproject dot org' GPG key: 0x7B30EE04E576AA84 GPG key server: https://keys.openpgp.org/

1 0

Re: [petsc-dev] Errors from PETSc 3.11 and 3.12 headers
by Balay, Satish 22 Dec '19

22 Dec '19

[petsc@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@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 > > >

1 0

Re: [petsc-dev] Errors from PETSc 3.11 and 3.12 headers
by Antonio Trande 22 Dec '19

22 Dec '19

On 22/12/19 20:32, 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 > > -- --- Antonio Trande Fedora Project mailto 'sagitter at fedoraproject dot org' GPG key: 0x7B30EE04E576AA84 GPG key server: https://keys.openpgp.org/

1 0

Re: [petsc-dev] Errors from PETSc 3.11 and 3.12 headers
by Antonio Trande 22 Dec '19

22 Dec '19

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 -- --- Antonio Trande Fedora Project mailto 'sagitter at fedoraproject dot org' GPG key: 0x7B30EE04E576AA84 GPG key server: https://keys.openpgp.org/

1 0

Re: [petsc-dev] Errors from PETSc 3.11 and 3.12 headers
by Balay, Satish 22 Dec '19

22 Dec '19

I guess one way to work around this issue is: diff --git a/include/petscksp.h b/include/petscksp.h index b75810337b..a201c97d3e 100644 --- a/include/petscksp.h +++ b/include/petscksp.h @@ -450,8 +450,6 @@ typedef enum {/* converged */ KSP_DIVERGED_NANORINF = -9, KSP_DIVERGED_INDEFINITE_MAT = -10, KSP_DIVERGED_PC_FAILED = -11, - KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED = -11, - KSP_CONVERGED_ITERATING = 0} KSPConvergedReason; PETSC_EXTERN const char *const*KSPConvergedReasons; Satish On Sun, 22 Dec 2019, 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 > > >>> > 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' > > CFLAGS='-fexceptions -fPIC -fstack-protector-strong -g -grecord-gcc-switches -m64 -mtune=generic -O2 -O3 --param=ssp-buffer-size=4 -pipe -pthread -Wall -Wp,-D_FORTIFY_SOURCE=2' > > <<<<< > > gcc (GCC) 9.2.1 20190827 (Red Hat 9.2.1-1) > > petscconf.h has: > > #define PETSC_DEPRECATED_ENUM(why) __attribute((deprecated)) > #define PETSC_DEPRECATED_FUNCTION(why) __attribute((deprecated)) > #define PETSC_DEPRECATED_MACRO(why) _Pragma(why) > #define PETSC_DEPRECATED_TYPEDEF(why) __attribute((deprecated)) > > > Satish > > On Sun, 22 Dec 2019, Smith, Barry F. wrote: > > > > > Please send configure.log and /usr/include/openmpi-x86_64/petsc/petscconf.h > > > > In theory our configure checks if deprecated can be used for Enums but perhaps our test is not complete. > > > > Barry > > > > > > > On Dec 22, 2019, at 12:01 PM, Antonio Trande <anto.trande(a)gmail.com> wrote: > > > > > > Hi all. > > > > > > I don't know of these are errors related to petsc4py or to PETSc, i'm > > > writing a mail to this mailing list too. > > > Issue reported to petsc4py folks: > > > https://bitbucket.org/petsc/petsc4py/issues/133/compiling-petsc4py-3110-aga… > > > > > > > > > In file included from /usr/include/openmpi-x86_64/petsc/petscsys.h:14:0, > > > from /usr/include/openmpi-x86_64/petsc/petscbag.h:4, > > > from /usr/include/openmpi-x86_64/petsc/petsc.h:5, > > > from src/petsc4py.PETSc.c:591, > > > from src/PETSc.c:4: > > > /usr/include/openmpi-x86_64/petsc/petscconf.h:85:36: error: expected ',' > > > or '}' before '__attribute' > > > #define PETSC_DEPRECATED_ENUM(why) __attribute((deprecated)) > > > ^ > > > /usr/include/openmpi-x86_64/petsc/petscksp.h:430:76: note: in expansion > > > of macro 'PETSC_DEPRECATED_ENUM' > > > #define KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED > > > KSP_DIVERGED_PCSETUP_FAILED PETSC_DEPRECATED_ENUM("Use > > > KSP_DIVERGED_PC_FAILED (since v3.11)") > > > > > > ^ > > > /usr/include/openmpi-x86_64/petsc/petscksp.h:452:15: note: in expansion > > > of macro 'KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED' > > > KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED = -11, > > > ^ > > > In file included from src/PETSc.c:4:0: > > > src/petsc4py.PETSc.c: In function '__pyx_f_8petsc4py_5PETSc_KSP_Converged': > > > src/petsc4py.PETSc.c:35723:22: error: 'KSP_CONVERGED_ITERATING' > > > undeclared (first use in this function) > > > (__pyx_v_r[0]) = KSP_CONVERGED_ITERATING; > > > ^ > > > src/petsc4py.PETSc.c:35723:22: note: each undeclared identifier is > > > reported only once for each function it appears in > > > src/petsc4py.PETSc.c: In function > > > '__pyx_pf_8petsc4py_5PETSc_3KSP_50callConvergenceTest': > > > src/petsc4py.PETSc.c:171473:20: error: 'KSP_CONVERGED_ITERATING' > > > undeclared (first use in this function) > > > __pyx_v_reason = KSP_CONVERGED_ITERATING; > > > ^ > > > src/petsc4py.PETSc.c: In function > > > '__pyx_pf_8petsc4py_5PETSc_3KSP_112getConvergedReason': > > > src/petsc4py.PETSc.c:174687:20: error: 'KSP_CONVERGED_ITERATING' > > > undeclared (first use in this function) > > > __pyx_v_reason = KSP_CONVERGED_ITERATING; > > > ^ > > > src/petsc4py.PETSc.c: In function '__pyx_pymod_exec_PETSc': > > > src/petsc4py.PETSc.c:303605:51: error: 'KSP_CONVERGED_ITERATING' > > > undeclared (first use in this function) > > > __pyx_t_7 = > > > __Pyx_PyInt_From_KSPConvergedReason(KSP_CONVERGED_ITERATING); if > > > (unlikely(!__pyx_t_7)) __PYX_ERR(37, 64, __pyx_L1_error) > > > ^ > > > error: command 'mpicc' failed with exit status > > > > > > > > > -- > > > --- > > > Antonio Trande > > > Fedora Project > > > mailto 'sagitter at fedoraproject dot org' > > > GPG key: 0x7B30EE04E576AA84 > > > GPG key server: https://keys.openpgp.org/ > > > > > >

1 0

Re: [petsc-dev] Errors from PETSc 3.11 and 3.12 headers
by Balay, Satish 22 Dec '19

22 Dec '19

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 >>> 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' CFLAGS='-fexceptions -fPIC -fstack-protector-strong -g -grecord-gcc-switches -m64 -mtune=generic -O2 -O3 --param=ssp-buffer-size=4 -pipe -pthread -Wall -Wp,-D_FORTIFY_SOURCE=2' <<<<< gcc (GCC) 9.2.1 20190827 (Red Hat 9.2.1-1) petscconf.h has: #define PETSC_DEPRECATED_ENUM(why) __attribute((deprecated)) #define PETSC_DEPRECATED_FUNCTION(why) __attribute((deprecated)) #define PETSC_DEPRECATED_MACRO(why) _Pragma(why) #define PETSC_DEPRECATED_TYPEDEF(why) __attribute((deprecated)) Satish On Sun, 22 Dec 2019, Smith, Barry F. wrote: > > Please send configure.log and /usr/include/openmpi-x86_64/petsc/petscconf.h > > In theory our configure checks if deprecated can be used for Enums but perhaps our test is not complete. > > Barry > > > > On Dec 22, 2019, at 12:01 PM, Antonio Trande <anto.trande(a)gmail.com> wrote: > > > > Hi all. > > > > I don't know of these are errors related to petsc4py or to PETSc, i'm > > writing a mail to this mailing list too. > > Issue reported to petsc4py folks: > > https://bitbucket.org/petsc/petsc4py/issues/133/compiling-petsc4py-3110-aga… > > > > > > In file included from /usr/include/openmpi-x86_64/petsc/petscsys.h:14:0, > > from /usr/include/openmpi-x86_64/petsc/petscbag.h:4, > > from /usr/include/openmpi-x86_64/petsc/petsc.h:5, > > from src/petsc4py.PETSc.c:591, > > from src/PETSc.c:4: > > /usr/include/openmpi-x86_64/petsc/petscconf.h:85:36: error: expected ',' > > or '}' before '__attribute' > > #define PETSC_DEPRECATED_ENUM(why) __attribute((deprecated)) > > ^ > > /usr/include/openmpi-x86_64/petsc/petscksp.h:430:76: note: in expansion > > of macro 'PETSC_DEPRECATED_ENUM' > > #define KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED > > KSP_DIVERGED_PCSETUP_FAILED PETSC_DEPRECATED_ENUM("Use > > KSP_DIVERGED_PC_FAILED (since v3.11)") > > > > ^ > > /usr/include/openmpi-x86_64/petsc/petscksp.h:452:15: note: in expansion > > of macro 'KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED' > > KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED = -11, > > ^ > > In file included from src/PETSc.c:4:0: > > src/petsc4py.PETSc.c: In function '__pyx_f_8petsc4py_5PETSc_KSP_Converged': > > src/petsc4py.PETSc.c:35723:22: error: 'KSP_CONVERGED_ITERATING' > > undeclared (first use in this function) > > (__pyx_v_r[0]) = KSP_CONVERGED_ITERATING; > > ^ > > src/petsc4py.PETSc.c:35723:22: note: each undeclared identifier is > > reported only once for each function it appears in > > src/petsc4py.PETSc.c: In function > > '__pyx_pf_8petsc4py_5PETSc_3KSP_50callConvergenceTest': > > src/petsc4py.PETSc.c:171473:20: error: 'KSP_CONVERGED_ITERATING' > > undeclared (first use in this function) > > __pyx_v_reason = KSP_CONVERGED_ITERATING; > > ^ > > src/petsc4py.PETSc.c: In function > > '__pyx_pf_8petsc4py_5PETSc_3KSP_112getConvergedReason': > > src/petsc4py.PETSc.c:174687:20: error: 'KSP_CONVERGED_ITERATING' > > undeclared (first use in this function) > > __pyx_v_reason = KSP_CONVERGED_ITERATING; > > ^ > > src/petsc4py.PETSc.c: In function '__pyx_pymod_exec_PETSc': > > src/petsc4py.PETSc.c:303605:51: error: 'KSP_CONVERGED_ITERATING' > > undeclared (first use in this function) > > __pyx_t_7 = > > __Pyx_PyInt_From_KSPConvergedReason(KSP_CONVERGED_ITERATING); if > > (unlikely(!__pyx_t_7)) __PYX_ERR(37, 64, __pyx_L1_error) > > ^ > > error: command 'mpicc' failed with exit status > > > > > > -- > > --- > > Antonio Trande > > Fedora Project > > mailto 'sagitter at fedoraproject dot org' > > GPG key: 0x7B30EE04E576AA84 > > GPG key server: https://keys.openpgp.org/ > > >

1 0

Re: [petsc-dev] Errors from PETSc 3.11 and 3.12 headers
by Smith, Barry F. 22 Dec '19

22 Dec '19

Please send configure.log and /usr/include/openmpi-x86_64/petsc/petscconf.h In theory our configure checks if deprecated can be used for Enums but perhaps our test is not complete. Barry > On Dec 22, 2019, at 12:01 PM, Antonio Trande <anto.trande(a)gmail.com> wrote: > > Hi all. > > I don't know of these are errors related to petsc4py or to PETSc, i'm > writing a mail to this mailing list too. > Issue reported to petsc4py folks: > https://bitbucket.org/petsc/petsc4py/issues/133/compiling-petsc4py-3110-aga… > > > In file included from /usr/include/openmpi-x86_64/petsc/petscsys.h:14:0, > from /usr/include/openmpi-x86_64/petsc/petscbag.h:4, > from /usr/include/openmpi-x86_64/petsc/petsc.h:5, > from src/petsc4py.PETSc.c:591, > from src/PETSc.c:4: > /usr/include/openmpi-x86_64/petsc/petscconf.h:85:36: error: expected ',' > or '}' before '__attribute' > #define PETSC_DEPRECATED_ENUM(why) __attribute((deprecated)) > ^ > /usr/include/openmpi-x86_64/petsc/petscksp.h:430:76: note: in expansion > of macro 'PETSC_DEPRECATED_ENUM' > #define KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED > KSP_DIVERGED_PCSETUP_FAILED PETSC_DEPRECATED_ENUM("Use > KSP_DIVERGED_PC_FAILED (since v3.11)") > > ^ > /usr/include/openmpi-x86_64/petsc/petscksp.h:452:15: note: in expansion > of macro 'KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED' > KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED = -11, > ^ > In file included from src/PETSc.c:4:0: > src/petsc4py.PETSc.c: In function '__pyx_f_8petsc4py_5PETSc_KSP_Converged': > src/petsc4py.PETSc.c:35723:22: error: 'KSP_CONVERGED_ITERATING' > undeclared (first use in this function) > (__pyx_v_r[0]) = KSP_CONVERGED_ITERATING; > ^ > src/petsc4py.PETSc.c:35723:22: note: each undeclared identifier is > reported only once for each function it appears in > src/petsc4py.PETSc.c: In function > '__pyx_pf_8petsc4py_5PETSc_3KSP_50callConvergenceTest': > src/petsc4py.PETSc.c:171473:20: error: 'KSP_CONVERGED_ITERATING' > undeclared (first use in this function) > __pyx_v_reason = KSP_CONVERGED_ITERATING; > ^ > src/petsc4py.PETSc.c: In function > '__pyx_pf_8petsc4py_5PETSc_3KSP_112getConvergedReason': > src/petsc4py.PETSc.c:174687:20: error: 'KSP_CONVERGED_ITERATING' > undeclared (first use in this function) > __pyx_v_reason = KSP_CONVERGED_ITERATING; > ^ > src/petsc4py.PETSc.c: In function '__pyx_pymod_exec_PETSc': > src/petsc4py.PETSc.c:303605:51: error: 'KSP_CONVERGED_ITERATING' > undeclared (first use in this function) > __pyx_t_7 = > __Pyx_PyInt_From_KSPConvergedReason(KSP_CONVERGED_ITERATING); if > (unlikely(!__pyx_t_7)) __PYX_ERR(37, 64, __pyx_L1_error) > ^ > error: command 'mpicc' failed with exit status > > > -- > --- > Antonio Trande > Fedora Project > mailto 'sagitter at fedoraproject dot org' > GPG key: 0x7B30EE04E576AA84 > GPG key server: https://keys.openpgp.org/ >

1 0

Errors from PETSc 3.11 and 3.12 headers
by Antonio Trande 22 Dec '19

22 Dec '19

Hi all. I don't know of these are errors related to petsc4py or to PETSc, i'm writing a mail to this mailing list too. Issue reported to petsc4py folks: https://bitbucket.org/petsc/petsc4py/issues/133/compiling-petsc4py-3110-aga… In file included from /usr/include/openmpi-x86_64/petsc/petscsys.h:14:0, from /usr/include/openmpi-x86_64/petsc/petscbag.h:4, from /usr/include/openmpi-x86_64/petsc/petsc.h:5, from src/petsc4py.PETSc.c:591, from src/PETSc.c:4: /usr/include/openmpi-x86_64/petsc/petscconf.h:85:36: error: expected ',' or '}' before '__attribute' #define PETSC_DEPRECATED_ENUM(why) __attribute((deprecated)) ^ /usr/include/openmpi-x86_64/petsc/petscksp.h:430:76: note: in expansion of macro 'PETSC_DEPRECATED_ENUM' #define KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED KSP_DIVERGED_PCSETUP_FAILED PETSC_DEPRECATED_ENUM("Use KSP_DIVERGED_PC_FAILED (since v3.11)") ^ /usr/include/openmpi-x86_64/petsc/petscksp.h:452:15: note: in expansion of macro 'KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED' KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED = -11, ^ In file included from src/PETSc.c:4:0: src/petsc4py.PETSc.c: In function '__pyx_f_8petsc4py_5PETSc_KSP_Converged': src/petsc4py.PETSc.c:35723:22: error: 'KSP_CONVERGED_ITERATING' undeclared (first use in this function) (__pyx_v_r[0]) = KSP_CONVERGED_ITERATING; ^ src/petsc4py.PETSc.c:35723:22: note: each undeclared identifier is reported only once for each function it appears in src/petsc4py.PETSc.c: In function '__pyx_pf_8petsc4py_5PETSc_3KSP_50callConvergenceTest': src/petsc4py.PETSc.c:171473:20: error: 'KSP_CONVERGED_ITERATING' undeclared (first use in this function) __pyx_v_reason = KSP_CONVERGED_ITERATING; ^ src/petsc4py.PETSc.c: In function '__pyx_pf_8petsc4py_5PETSc_3KSP_112getConvergedReason': src/petsc4py.PETSc.c:174687:20: error: 'KSP_CONVERGED_ITERATING' undeclared (first use in this function) __pyx_v_reason = KSP_CONVERGED_ITERATING; ^ src/petsc4py.PETSc.c: In function '__pyx_pymod_exec_PETSc': src/petsc4py.PETSc.c:303605:51: error: 'KSP_CONVERGED_ITERATING' undeclared (first use in this function) __pyx_t_7 = __Pyx_PyInt_From_KSPConvergedReason(KSP_CONVERGED_ITERATING); if (unlikely(!__pyx_t_7)) __PYX_ERR(37, 64, __pyx_L1_error) ^ error: command 'mpicc' failed with exit status -- --- Antonio Trande Fedora Project mailto 'sagitter at fedoraproject dot org' GPG key: 0x7B30EE04E576AA84 GPG key server: https://keys.openpgp.org/

1 0

Re: [petsc-dev] Testing a new configure addition
by Matthew Knepley 19 Dec '19

19 Dec '19

On Thu, Dec 19, 2019 at 12:54 PM Balay, Satish <balay(a)mcs.anl.gov> wrote: > update one [or more] tests with this package - i.e add --download-package > to one or more config/examples/arch-ci-*.py - and run this change through > MR/CI > > And if this new package is added in a branch/MR - then the tests configure > scripts are best updated in the same branch/MR > Thanks! Matt > Satish > > On Thu, 19 Dec 2019, Matthew Knepley wrote: > > > How do I test a new package added to configure? > > > > Thanks, > > > > Matt > > > > > > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>

1 0