<div dir="ltr"><div class="gmail_quote">On Thu, Feb 2, 2012 at 21:30, Jeff Hammond <span dir="ltr"><<a href="mailto:jhammond@alcf.anl.gov">jhammond@alcf.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":11t">(This question belongs on <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a>)<div><br></div><div>It seems that you are using mpiexec from OpenMPI with a binary compiled with MPICH2. This is not a good idea.</div>
<div><br></div><div>Please use the mpiexec from MPICH2. If you do not know where it is, try 'find /home/<span style="font-size:medium">mpich2-1.4.1p1/ -name mpiexec'.</span></div><div><br>You can see what mpiexec you are using by calling 'which mpiexec'.</div>
</div></blockquote></div><br><div>This problem is way too common. Why doesn't mpiexec put some token in the environment that MPI_Init() can check and error if it doesn't match (including version, if necessary)? Same with Open MPI. The error message could even helpfully point out the location of the correct mpiexec.</div>
</div>