Hi all, It turns out that this is a problem in PETSc caused by a "fix" to a different OSX problem. We have reverted the offending commit on the firedrake/petsc fork so hopefully updating now should fix the issue. Please scream immediately if it does not. Regards, David On Tue, 24 Nov 2015 at 22:23 David Ham <David.Ham@imperial.ac.uk> wrote:
Reproduced. Very odd, it seems petsc4py is currently borked. I don't understand where this library location is coming from. It certainly isn't where the petsc python module reports the python being installed.
On Tue, 24 Nov 2015 at 22:06 David Ham <David.Ham@imperial.ac.uk> wrote:
OK. I'm doing a scratch rebuild to see if I can reproduce this.
David
On Tue, 24 Nov 2015 at 21:33 Justin Chang <jychang48@gmail.com> wrote:
Hi all,
Just wanted to say that I am also now having these exact same issues as others after updating Firedrake on my mac.
Thanks, Justin
On Tue, Nov 24, 2015 at 6:11 AM, Lawrence Mitchell < lawrence.mitchell@imperial.ac.uk> wrote:
On 23/11/15 16:52, Wingate, Beth wrote:
module = imp.load_module(fullname, fo, fn, stuff) ImportError:
dlopen(/Users/wingate/firedrake/lib/python2.7/site-packages/petsc4py/lib/PETSc.so,
2): Library not loaded:
/private/var/folders/rw/1wgmdvd50sv7bb1dksy4y_l00000gq/T/pip-DOH6bI-build/arch-python-macosx-10.11-x86_64/lib/libpetsc.3.06.dylib
Referenced from:
/Users/wingate/firedrake/lib/python2.7/site-packages/petsc4py/lib/PETSc.so
Reason: image not found
Hmph, petsc4py has linked against the temporary location of libpetsc (which appeared via pip presumably), rather than its final location.
It is not immediately obvious to me why this would be the case. I do not think it is likely anything wrong with your build setup though.
Lawrence
_______________________________________________ firedrake mailing list firedrake@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/firedrake