Hi all,
Sorry for the long Layoff on this but I have been dealing with other
issues. I'll report what I've learned then answer Jeff's questions.
First of all Doug Reeder is correct in saying the Apple supplied Open
MPI is conflicting. Furthermore, it conflicts with both shared and
static libr
Hello,
You may me bumping into conflicts between the apple supplied ompi and your mpi.
I use modules to force my mpi to the front of the PATH and DYLD_LIBRARY_PATH
variables.
Doug Reeder
On Dec 15, 2010, at 5:22 PM, Jeff Squyres wrote:
> Sorry for the ginormous delay in replying here; I blame
On 12/15/2010 8:22 PM, Jeff Squyres wrote:
Sorry for the ginormous delay in replying here; I blame SC'10, Thanksgiving,
and the MPI Forum meeting last week...
On Nov 29, 2010, at 2:12 PM, David Robertson wrote:
I'm noticing a strange problem with Open MPI 1.4.2 on Mac OS X 10.6. We use
both
Sorry for the ginormous delay in replying here; I blame SC'10, Thanksgiving,
and the MPI Forum meeting last week...
On Nov 29, 2010, at 2:12 PM, David Robertson wrote:
> I'm noticing a strange problem with Open MPI 1.4.2 on Mac OS X 10.6. We use
> both Intel Ifort 11.1 and gfortran 4.3 on the
Hi all,
I'm noticing a strange problem with Open MPI 1.4.2 on Mac OS X 10.6. We
use both Intel Ifort 11.1 and gfortran 4.3 on the same machine and
switch between them to test and debug code.
I had runtime problems when I compiled openmpi in my usual way of no
shared libraries so I switched t
