From: Jo Shields (jo.shields_at_[hidden])
Date: 2008-10-22 13:37:03
On Wed, 2008-10-22 at 13:13 -0400, Ben Martin wrote:
> Hmmm. Two things occur to me. The first is, be sure to rerun configure
> when changing which MPI implementation you're building against. I assume
> you're probably already doing that, but, just in case...
> The second is that while in theory MPI.NET should just build against any
> MPI, in practice there's no way to be sure in advance. I know that it
> works with OpenMPI and MPICH2. If when you say MPICH you mean MPICH2,
> then it should have built. You might try it with OpenMPI just to see if
> it builds.
> If it's failing against OpenMPI or even MPICH2, then I'll probably need
> more information to figure out the problem, since I'm able to build both
> on Linux without a problem. Could you tell me more about the system,
> like distro and architecture? You might also check the version of perl
> since it's a perl script that generates CustomUnsafe.cs.
It seems it's an MPICH1 (and MPICH1-compatibles) issue. The
MPI_HANDLES_ARE_POINTERS is set when compiling against the three MPIs I
mentioned, and it's that macro which prevents compilation.
Building against OpenMPI works fine