-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 14/07/15 11:23, Justin Chang wrote:
python -c "import pyop2; pyop2.init(); print pyop2.__version__" gives the following:
OK, thanks. I think we're nearly there. This backtrace points at
/usr/lib/libmpi.so.1(MPI_Comm_set_errhandler+0x4d) [0x7f83c5be3a1d]
The globally installed MPI. But all the link output points to:
libmpi.so.12 => /home/justin/Software/petsc-dev/arch-linux2-c-opt/lib/libmpi.so.12 (0x00007f780047c000) libmpifort.so.12 => /home/justin/Software/petsc-dev/arch-linux2-c-opt/lib/libmpifort.so.12
(0x00007f77fe670000) I.e. the MPI version petsc has built for you. I therefore suspect that the issue is coming from an mpi4py installation that is linked against /usr/lib/libmpi.so (rather than the $PETSC_DIR/$PETSC_ARCH/lib/libmpi.so). Does the following sequence result in the same set of errors? python -c "from mpi4py import MPI; from petsc4py import PETSc" If so, I think the solution is to install mpi4py linked against the same MPI library that petsc and friends are using. Cheers, Lawrence -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVpOSaAAoJECOc1kQ8PEYvkVsH/3MRr3/W1K7oCoRP0Cranr1h IG62KO69/3OP2aA0WjrLXiShK/RBPhHUv3oLzx2wbQUPxuaRIT2uBmrWpH+MJmik j//dYtHrvgXqYPSs2DWNAE0nYJ/6f+AOCtj59gTzT7Wy17h2Vw1brE04eei3qjK2 dJgcMpYrGiYEa+/j6lW/z+q29eODFBAUkbUIRS3hfHxmR63LNSgKLdaUHRFOWZy2 njjTD9JlSobtfLJGWUgMKPaJSdki4+tbr0XmLdMl5CsPcLzTtOW3FrODSu5ZRPt7 shfOSGh7ATrXZ4ioA0JAxDjUcGt7Qyu29ZJ3GntQAX/7ZTEvzOSIj1RgMNChYdM= =tigp -----END PGP SIGNATURE-----