<!DOCTYPE html>
<!-- BaNnErBlUrFlE-BoDy-start -->
<!-- Preheader Text : BEGIN -->
<div style="display:none !important;display:none;visibility:hidden;mso-hide:all;font-size:1px;color:#ffffff;line-height:1px;height:0px;max-height:0px;opacity:0;overflow:hidden;">
Best to get latest petsc and build petsc4py along with petsc: For example: balay@ petsc-gpu-02: /scratch/balay$ wget -q https: //urldefense. us/v3/__https: //web. cels. anl. gov/projects/petsc/download/release-snapshots/petsc-3. 21. 2. tar. gz__;!!G_uCfscf7eWS!cU65HojMoX4qnDw9h2E_i8frWwq0jfbCEShSCwMh_szcyzQQjPEkofz46mtT2_QUECgsaJ8X1EeiirH57Detjy16b-M$
</div>
<!-- Preheader Text : END -->
<!-- Email Banner : BEGIN -->
<div style="display:none !important;display:none;visibility:hidden;mso-hide:all;font-size:1px;color:#ffffff;line-height:1px;height:0px;max-height:0px;opacity:0;overflow:hidden;">ZjQcmQRYFpfptBannerStart</div>
<!--[if ((ie)|(mso))]>
<table border="0" cellspacing="0" cellpadding="0" width="100%" style="padding: 16px 0px 16px 0px; direction: ltr" ><tr><td>
<table border="0" cellspacing="0" cellpadding="0" style="padding: 0px 10px 5px 6px; width: 100%; border-radius:4px; border-top:4px solid #90a4ae;background-color:#D0D8DC;"><tr><td valign="top">
<table align="left" border="0" cellspacing="0" cellpadding="0" style="padding: 4px 8px 4px 8px">
<tr><td style="color:#000000; font-family: 'Arial', sans-serif; font-weight:bold; font-size:14px; direction: ltr">
This Message Is From an External Sender
</td></tr>
<tr><td style="color:#000000; font-weight:normal; font-family: 'Arial', sans-serif; font-size:12px; direction: ltr">
This message came from outside your organization.
</td></tr>
</table>
</td></tr></table>
</td></tr></table>
<![endif]-->
<![if !((ie)|(mso))]>
<div dir="ltr" id="pfptBanneriz3e0sm" style="all: revert !important; display:block !important; text-align: left !important; margin:16px 0px 16px 0px !important; padding:8px 16px 8px 16px !important; border-radius: 4px !important; min-width: 200px !important; background-color: #D0D8DC !important; background-color: #D0D8DC; border-top: 4px solid #90a4ae !important; border-top: 4px solid #90a4ae;">
<div id="pfptBanneriz3e0sm" style="all: unset !important; float:left !important; display:block !important; margin: 0px 0px 1px 0px !important; max-width: 600px !important;">
<div id="pfptBanneriz3e0sm" style="all: unset !important; display:block !important; visibility: visible !important; background-color: #D0D8DC !important; color:#000000 !important; color:#000000; font-family: 'Arial', sans-serif !important; font-family: 'Arial', sans-serif; font-weight:bold !important; font-weight:bold; font-size:14px !important; line-height:18px !important; line-height:18px">
This Message Is From an External Sender
</div>
<div id="pfptBanneriz3e0sm" style="all: unset !important; display:block !important; visibility: visible !important; background-color: #D0D8DC !important; color:#000000 !important; color:#000000; font-weight:normal; font-family: 'Arial', sans-serif !important; font-family: 'Arial', sans-serif; font-size:12px !important; line-height:18px !important; line-height:18px; margin-top:2px !important;">
This message came from outside your organization.
</div>
</div>
<div style="clear: both !important; display: block !important; visibility: hidden !important; line-height: 0 !important; font-size: 0.01px !important; height: 0px"> </div>
</div>
<![endif]>
<div style="display:none !important;display:none;visibility:hidden;mso-hide:all;font-size:1px;color:#ffffff;line-height:1px;height:0px;max-height:0px;opacity:0;overflow:hidden;">ZjQcmQRYFpfptBannerEnd</div>
<!-- Email Banner : END -->
<!-- BaNnErBlUrFlE-BoDy-end -->
<html>
<head><!-- BaNnErBlUrFlE-HeAdEr-start -->
<style>
#pfptBanneriz3e0sm { all: revert !important; display: block !important;
visibility: visible !important; opacity: 1 !important;
background-color: #D0D8DC !important;
max-width: none !important; max-height: none !important }
.pfptPrimaryButtoniz3e0sm:hover, .pfptPrimaryButtoniz3e0sm:focus {
background-color: #b4c1c7 !important; }
.pfptPrimaryButtoniz3e0sm:active {
background-color: #90a4ae !important; }
</style>
<!-- BaNnErBlUrFlE-HeAdEr-end -->
<meta charset="US-ASCII"></head><body><pre style="font-family: sans-serif; font-size: 100%; white-space: pre-wrap; word-wrap: break-word">Best to get latest petsc and build petsc4py along with petsc:
For example:
balay@petsc-gpu-02:/scratch/balay$ wget -q <a href="https://urldefense.us/v3/__https://web.cels.anl.gov/projects/petsc/download/release-snapshots/petsc-3.21.2.tar.gz__;!!G_uCfscf7eWS!cU65HojMoX4qnDw9h2E_i8frWwq0jfbCEShSCwMh_szcyzQQjPEkofz46mtT2_QUECgsaJ8X1EeiirH57Detjy16b-M$">https://urldefense.us/v3/__https://web.cels.anl.gov/projects/petsc/download/release-snapshots/petsc-3.21.2.tar.gz__;!!G_uCfscf7eWS!cU65HojMoX4qnDw9h2E_i8frWwq0jfbCEShSCwMh_szcyzQQjPEkofz46mtT2_QUECgsaJ8X1EeiirH57Detjy16b-M$</a>
balay@petsc-gpu-02:/scratch/balay$ tar -xf petsc-3.21.2.tar.gz
balay@petsc-gpu-02:/scratch/balay$ cd petsc-3.21.2/
balay@petsc-gpu-02:/scratch/balay/petsc-3.21.2$ ./configure --download-mpich --download-fblaslapack --download-mpi4py --with-petsc4py=1 && make && make check && make petsc4pytest
=============================================================================================
Configuring PETSc to compile on your system
=============================================================================================
<snip>
testPlaceArray (test_vec.TestVecShared) ... ok
testPlaceArray (test_vec.TestVecShared) ... ok
<snip>
Ran 6154 tests in 134.314s
OK
=====================================
balay@petsc-gpu-02:/scratch/balay/petsc-3.21.2$
Satish
On Tue, 25 Jun 2024, Stefano Zampini wrote:
> Which version of petsc4py is it?
>
> Il giorno mar 25 giu 2024 alle ore 20:35 maitri ksh <maitri.ksh@gmail.com>
> ha scritto:
>
> > I am currently working on integrating petsc4py, but I am encountering
> > persistent compilation issues related to Cython. Below are the details of
> > my setup and the errors I am facing. I would greatly appreciate any
> > assistance or guidance on how
> > ZjQcmQRYFpfptBannerStart
> > This Message Is From an External Sender
> > This message came from outside your organization.
> >
> > ZjQcmQRYFpfptBannerEnd
> >
> > I am currently working on integrating petsc4py, but I am encountering
> > persistent compilation issues related to Cython. Below are the details of
> > my setup and the errors I am facing. I would greatly appreciate any
> > assistance or guidance on how to resolve these issues.
> > System Configuration:
> >
> > - *PETSc Architecture*: linux-gnu-c-debug
> > - *Python Environment*: Python 3.6 (virtual environment)
> > - *Cython Version*: 3.0.10
> > - *Compiler*: /gcc11.2/bin/gcc
> >
> > During the build process, I received multiple warnings and errors related
> > to the use of noexcept, nogil, and except in function declarations. Here
> > are some of the specific errors:
> >
> > cythonizing 'petsc4py.PETSc.pyx' -> 'petsc4py.PETSc.c'
> > warning: petsc4py.PETSc.pyx:1:0: Dotted filenames ('petsc4py.PETSc.pyx')
> > are deprecated. Please use the normal Python package directory layout.
> > /home/maitri.ksh/Maitri/petsc/petsc4py/myenv/lib64/python3.6/site-packages/Cython/Compiler/Main.py:381:
> > FutureWarning: Cython directive 'language_level' not set, using '3str' for
> > now (Py3). This has changed from earlier releases! File:
> > include/petsc4py/PETSc.pxd
> > tree = Parsing.p_module(s, pxd, full_module_name)
> > warning: PETSc/PETSc.pyx:53:48: The keyword 'nogil' should appear at the
> > end of the function signature line. Placing it before 'except' or
> > 'noexcept' will be disallowed in a future version of Cython.
> > warning: PETSc/petscvec.pxi:406:79: The keyword 'nogil' should appear at
> > the end of the function signature line. Placing it before 'except' or
> > 'noexcept' will be disallowed in a future version of Cython.
> > warning: PETSc/petscvec.pxi:411:79: The keyword 'nogil' should appear at
> > the end of the function signature line. Placing it before 'except' or
> > 'noexcept' will be disallowed in a future version of Cython.
> > ...
> >
> > Error compiling Cython file:
> > ...
> > PETSc/petscobj.pxi:91:29: Cannot assign type 'int (void *) except? -1
> > nogil' to 'int (*)(void *) noexcept'. Exception values are incompatible.
> > Suggest adding 'noexcept' to the type of 'PetscDelPyDict'.
> > ...
> > PETSc/cyclicgc.pxi:34:20: Cannot assign type 'int (PyObject *, visitproc,
> > void *) except? -1' to 'traverseproc *'. Exception values are incompatible.
> > Suggest adding 'noexcept' to the type of 'tp_traverse'.
> > ...
> > PETSc/cyclicgc.pxi:35:20: Cannot assign type 'int (PyObject *) except? -1'
> > to 'inquiry *'. Exception values are incompatible. Suggest adding
> > 'noexcept' to the type of 'tp_clear'.
> > ...
> > PETSc/PETSc.pyx:351:17: Cannot assign type 'void (void) except * nogil' to
> > 'void (*)(void) noexcept'. Exception values are incompatible. Suggest
> > adding 'noexcept' to the type of 'finalize'.
> > error: Cython failure: 'petsc4py.PETSc.pyx' -> 'petsc4py.PETSc.c'
> >
> > Any advice on building petsc4py in environments similar to mine would be
> > greatly appreciated.
> > Thanks,
> > Maitri
> >
>
>
>
</pre></body></html>