On 1/29/2015 12:04 PM, Eike Mueller wrote:
Hi Florian,
I recall having similar issues with incompatible MPI versions before, but can't find anything in my emails which points to a solution. I think the reason in my case was that the CRAY MPICH was updated at some point after the original /work/y07/y07/fdrake installation, but before I installed my own version.
I would have expected something like this, but afaict we were using mpich 7.0.3 throughout.
Could it be that mpi4py is still using the old MPICH and needs to be reinstalled?
That is indeed a possibility. I wonder if you could get access to the fdrake account since you're pretty much the main user. Michael? Florian
Cheers,
Eike
On 29/01/15 11:51, Florian Rathgeber wrote:
On 29/01/15 10:23, Eike Mueller wrote:
I need to install my own version of FFC, since the one already installed in /work/y07/y07/fdrake appears not to be compatible with the firedrake version I use
I had a go at updating the "official" firedrake package on ARCHER and dependencies. I updated PETSc and petsc4py to the latest revision of the respective firedrake branch. Then I failed however building the firedrake extension modules due to the following error:
/work/y07/y07/fdrake/petsc/include/petscsys.h:124:6: error: #error "PETSc was configured with one MPICH mpi.h v ersion but now appears to be compiling using a different MPICH mpi.h version"
afaict we always use cray-mpich/7.0.3 for building petsc and everything else. No idea what triggers this error.
On another note: I *really* don't have time to continue maintaining the fdrake modules on ARCHER and appreciate if someone else (Michael? Lawrence?) could take on this task. I also don't have time to sort out this current issue, sorry about that.
Florian