That's a good point. Make sure that 'which mpicc' is grabbing the MacPorts (assuming standard /opt/local install) /opt/local/bin/mpicc and not /usr/bin/mpicc (which ships with OSX since Leopard, if I recall) .. And use the wrappers rather than putting your include and link paths for MPI into your makefile / XCode project.<div>
<br></div><div> -Eric<br><br><div class="gmail_quote">On Fri, Mar 11, 2011 at 12:59 AM, Anthony Chan <span dir="ltr"><<a href="mailto:chan@mcs.anl.gov">chan@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
there could be multiple problem in your MPI installation<br>
or compilation of icarus_mac.exe.<br>
<br>
----- Original Message -----<br>
<br>
> theron$ mpiexec -np 2 icarus_mac.exe <<a href="http://steady_slowest.in" target="_blank">steady_slowest.in</a><br>
> Fatal error in MPI_Comm_rank: Invalid communicator, error stack:<br>
> MPI_Comm_rank(106): MPI_Comm_rank(comm=0x1, rank=0x1001ecd04) failed<br>
> MPI_Comm_rank(64).: Invalid communicator<br>
<br>
The usual reason for "invalid communicator" error is including incorrect<br>
MPI header file in creating icarus_mac.exe. Are there multiple MPI installations<br>
on your mac ? Did you use MPI wrappers, i.e. mpicc/mpif77, in building<br>
icarus_mac.exe ?<br>
<br>
> rank 0 in job 15 comp.local_53650 caused collective abort of all ranks<br>
> exit status of rank 0: return code 1<br>
<br>
A.Chan<br>
<div><div></div><div class="h5">_______________________________________________<br>
mpich-discuss mailing list<br>
<a href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a><br>
<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a><br>
</div></div></blockquote></div><br>
</div>