Dear Patrick, Thomas, [note: writing email directly to me to try and solve problems with Firedrake is not the way to get a fast response. Please send issues to the Firedrake mailing list (cc'd now)]
On 11 Dec 2016, at 11:20, Patrick Farrell <patrick.farrell@maths.ox.ac.uk> wrote:
Dear Lawrence,
A colleague of mine, Thomas Surowiec, is trying to install firedrake on OSX 10.10.3. Unfortunately the firedrake-install script isn't working out of the box.
It appears that OSX has decided to put mpif90 in /usr/local/Cellar/open-mpi/1.10.2/bin/mpif90, but the PETSc compilation is looking for it in /usr/local/bin/. Any idea why, or what we can do?
What does: $ env $ which mpif90 $ which gfortran $ which python $ cat > foo.f90 << \EOF program main use mpi end $ mpif90 foo.f90 Give? It looks like the MPI compiler is somehow not working?
-------- Forwarded Message -------- Subject: Re: Firedrake Date: Sun, 11 Dec 2016 12:06:26 +0100 From: Thomas Surowiec <thomas.surowiec@gmail.com> To: Patrick Farrell <patrick.farrell@maths.ox.ac.uk>
Still a mess. It went a few steps further, but there were problems with the security features. In case you're interested the complete output is below. Are there now several half compiled versions and folders associated with fenics and firedrake on my system? Is there anyway to delete all of them and start over?
Other than the homebrew dependencies, firedrake-install puts *everything* inside the "firedrake" subdirectory of the working directory that you ran firedrake-install in. You can safely just delete this subtree.
ThomasSsMacBook:~ anounz$ /usr/bin/python firedrake-install
All of our testing is done with the homebrew python, rather than the system python. I do not know if this will cause issues, but all of us with Mac systems use the python that homebrew puts in /usr/local/bin. Lawrence