petsc4py fails to configure with my own lapack/blas

Ondrej Certik ondrej at
Thu Jun 4 18:18:17 CDT 2009

On Thu, Jun 4, 2009 at 5:14 PM, Lisandro Dalcin<dalcinl at> wrote:
> On Thu, Jun 4, 2009 at 7:59 PM, Ondrej Certik <ondrej at> wrote:
>> On Thu, Jun 4, 2009 at 4:13 PM, Lisandro Dalcin<dalcinl at> wrote:
>>> This smells to a 32/64 bit libs mismatch, or a g77/g95/gfortran
>>> mismatch. Addionally, could you try to run 'ldd' on core PETSc libs
>>> and on the extension module?
>> So those core PETSc libs are just .a libraries (not dynamic
>> executables). Could that be a problem?
> That could be a BIG problem. petsc4py does not "officially" support
> PETSc builds with static libs, though it could work on some scenarios.
> Moreover, even if you get it working, you will not be able to use let
> say slepc4py, or any other C code depending on the PETSc libraries
> (think of a fast, Cython-implemented Function()/Jacobian() routine for
> a nonlinear problem solved with SNES).
> I really recommend you to pass '--with-shared' to PETSc's configure.

Ah, I didn't know I have to pass it. I thought petsc will do the right
thing. Let me do it right now and I'll report back.


More information about the petsc-users mailing list