Thanks. Perhaps that would have worked. What I ended up doing was "hiding" the headers, libs, and exes for the openmpi that came installed on the mac. Then I did the configure, make, and make install again, and it worked.<br>
<br>-thomas<br><br><div class="gmail_quote">On Wed, Dec 17, 2008 at 11:12 PM, Rajeev Thakur <span dir="ltr"><<a href="mailto:thakur@mcs.anl.gov">thakur@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2">Just try logging out and log back in
again.</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2">Rajeev</font></span></div><br>
<blockquote style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div dir="ltr" align="left" lang="en-us">
<hr>
<font face="Tahoma" size="2"><b>From:</b> <a href="mailto:mpich-discuss-bounces@mcs.anl.gov" target="_blank">mpich-discuss-bounces@mcs.anl.gov</a>
[mailto:<a href="mailto:mpich-discuss-bounces@mcs.anl.gov" target="_blank">mpich-discuss-bounces@mcs.anl.gov</a>] <b>On Behalf Of </b>Thomas
Blom<br><b>Sent:</b> Wednesday, December 17, 2008 10:06 PM<br><b>To:</b>
<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br><b>Subject:</b> [mpich-discuss] mpich2 / openmpi
conflicts on osx 10.5?<br></font><br></div><div><div></div><div class="Wj3C7c">
<div></div>Hello,<br><br>I've successfully used mpich2 on windows and on a
couple of other osx machines, but having just built mpich2 from source on a
new mac pro I encounter difficulty when trying to run some mpi
programs.<br><br>OSX 10.5 ships with OpenMPI apparently, such that there are
mpi* programs in /usr/bin<br><br>I accepted the default when
configuring/building/installing mpich2, such that it gets installed to
/usr/local/bin<br><br>Once I realized that the wrong mpiexec was getting
called, I chose to "hide" the /usr/bin versions (not knowing otherwise how to
disable or uninstall the openmpi) by just creating a folder _mpi_hidden in
/usr/bin and placing all those mpi* programs in there.<br><br>Now when I type
"which mpiexec" it correctly states /usr/local/bin/mpiexec (the mpich2
installed version)<br><br>But when I try the example "mpiexec -n 3 hostname" I
get the error message<br><br>-bash: /usr/bin/mpiexec: No such file or
directory<br><br>I'm not clear about what's going on here. Is the python
mpiexec in /usr/local/bin trying to call the preexisting mpiexec in
/usr/bin?<br><br>The original mpiexec in /usr/bin reports this when run
without argument<br><br>mpiexec (OpenRTE) 1.2.3<br><usage/flags
snipped><br><br>Thanks for any help untangling this problem. I'm not
sure why I didn't run into this problem on a new imac that was setup similarly
a couple months ago...Perhaps OS preinstalled on that system was an earlier
rev of 10.5. For whatever reason it does not have any mpi programs in
/usr/bin.<br><br>-thomas blom<br>ices/ut
austin<br><br><br><br><br><br></div></div></blockquote></div>
</blockquote></div><br>