petsc4py fails to configure with my own lapack/blas

[Ondrej Certik]

On Thu, Jun 4, 2009 at 4:13 PM, Lisandro Dalcin<dalcinl at gmail.com> 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 PETSc.so extension module?

So those core PETSc libs are just .a libraries (not dynamic
executables). Could that be a problem?

As to PETSc.so:

$ ldd lib/linux-gnu-c-debug/PETSc.so
	linux-vdso.so.1 =>  (0x00007fff551ff000)
	libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f1b4c0c1000)
	libcblas.so.3gf => /usr/lib/libcblas.so.3gf (0x00007f1b4bea2000)
	libf77blas.so.3gf => /usr/lib/libf77blas.so.3gf (0x00007f1b4bc83000)
	libatlas.so.3gf => /usr/lib/libatlas.so.3gf (0x00007f1b4b2fd000)
	libdl.so.2 => /lib/libdl.so.2 (0x00007f1b4b0d9000)
	libmpi.so.0 => /usr/lib/libmpi.so.0 (0x00007f1b4ae36000)
	libopen-rte.so.0 => /usr/lib/libopen-rte.so.0 (0x00007f1b4abee000)
	libopen-pal.so.0 => /usr/lib/libopen-pal.so.0 (0x00007f1b4a982000)
	libnsl.so.1 => /lib/libnsl.so.1 (0x00007f1b4a768000)
	libutil.so.1 => /lib/libutil.so.1 (0x00007f1b4a565000)
	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007f1b4a34c000)
	libpthread.so.0 => /lib/libpthread.so.0 (0x00007f1b4a130000)
	libmpi_f90.so.0 => /usr/lib/libmpi_f90.so.0 (0x00007f1b49f2c000)
	libmpi_f77.so.0 => /usr/lib/libmpi_f77.so.0 (0x00007f1b49cf3000)
	libgfortran.so.3 => /usr/lib/libgfortran.so.3 (0x00007f1b49a17000)
	libm.so.6 => /lib/libm.so.6 (0x00007f1b49792000)
	libc.so.6 => /lib/libc.so.6 (0x00007f1b4941f000)
	libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f1b49203000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f1b4d0f7000)
	libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f1b48fff000)
	libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f1b48dfa000)


So I don't know...

Ondrej