On 2018-08-31 22:32, Graham Inggs wrote:
Hi On 30 August 2018 at 10:39, Drew Parsons <dparsons@debian.org> wrote:It's a comedy of errors with openmpi3, I see 3.1.2 has triggered new RC bugsTo be clear, 3.1.2 didn't introduce any new RC bugs. The bugs you see here [1] affect the version in testing and should not block migration.What is delaying openmpi's migration is dolfin's autopkgtest failure [2].
That's weird. Looks like the problem comes through PETScfrom /tmp/autopkgtest-lxc.g876mqve/downtmp/build.W96/src/dolfin-demo/documented/auto-adaptive-poisson/cpp/main.cpp:14: /usr/include/dolfin/common/types.h:24:10: fatal error: petscsys.h: No such file or directory
#include <petscsys.h>petscsys.h is located at /usr/lib/petscdir/petsc3.9/x86_64-linux-gnu-real/include with the dir registered in dolfin.pc. I think dolfin stopped finding it because of a failure testing PetscInt during the cmake configuration. It's not clear if that failure is a consequence of the warning about the path to openmpi's libevent or not.
I'll ask upstream if it means we need to rebuild dolfin or petsc. Drew