Hi Lawrence, System is down now - will test as soon as I can. Bob Bob Cregan HPC Systems Analyst Information & Communication Technologies Imperial College London, South Kensington Campus London, SW7 2AZ T: 07712388129 E: b.cregan@imperial.ac.uk W: www.imperial.ac.uk/ict/rcs<http://www.imperial.ac.uk/ict/rcs> [1505984389175_twitter.png] @imperialRCS @imperialRSE [1505983882959_Imperial-RCS.png] ________________________________ From: Lawrence Mitchell <wence@gmx.li> Sent: 25 March 2019 11:26 To: Cregan, Bob Cc: firedrake; Lacalle Puig, Santiago Subject: Re: [firedrake] Build issue on Imperial clusters/Intel CC Hi Bob, I think we have now managed to fix this in firedrake-install. Can you try things out and let us know? You'll need to get a new version from the download page and then do: firedrake-install --your-args --mpicc /path/to/mpicc --mpicxx /path/to/mpicxx --mpif90 /path/to/mpif90 --mpiexec /path/to/mpiexec This does two things: 1. Ensure that compilers are set correctly when we install things 2. Adds symlinks from firedrake/bin/{mpicc, mpicxx, ...} to the provided MPI compilers in the virtualenv (this way, in an activated virtualenv, the compilers all point at the right place). Cheers, Lawrence
On 20 Mar 2019, at 12:07, Lawrence Mitchell <wence@gmx.li> wrote:
On 20 Mar 2019, at 11:54, Cregan, Bob <b.cregan@imperial.ac.uk> wrote:
Hi See attached - not sure what build options were used for that particular one had to get from backup.
Setting the compiler works for all the various sub-builds - it was just PyOP2 that could not find the mpi header files.
Ah thanks. It looks like we are not careful about how we control environment variables for various subbuilds.
c.f. here https://github.com/firedrakeproject/firedrake/issues/1396
Lawrence
