Hello Jeff, Eugene:
On Fri, Dec 12, 2008 at 04:47:11PM -0500, Jeff Squyres wrote:
..
> The "P" is MPI's profiling interface. See chapter 14 in the MPI-2.1
> doc.
Ah...Thank you, both Jeff and Eugene, for pointing that out.
I think there is a typo in chapter 14 - the first sentence isn't
Jeroen Kleijer wrote:
However, if you're able to compile and use a version of the
development branch (1.3) you should be use compile and run the "hello
world" program without problems, regardless of the subnet they're in.
I installed 1.3rc2 and that seems to have done the trick.
On a side note
Hello,
The below FAQ lists instructions on how to use a relocated Open MPI
installation:
http://www.open-mpi.org/faq/?category=building#installdirs
On Solaris, OPAL_PREFIX and friends (documented in the FAQ) work for
me with both MPI (hello_c) and non-MPI (hostname) programs. On Linux,
I can o
Jeroen Kleijer wrote:
The stable branch (1.2.x) works perfectly but _only_ when the
communication channel between machines are in the same subnet.
(ethernet)
Since you don't have that much control over which subnet your machines
get in, OpenMPI has a tendency to fail in Amazon's EC2.
However, if
Hi,
> After compiling it, I copied it over to the other machine and tried
> running it with:
>
> mpirun -v --mca btl self,tcp -np 4 --machinefile machines /mnt/mpihw
>
> which produces:
[.]
> AFAIK, the machines are able to communicate with each other on any port
> you like, just not with MP
I've been trying to get OpenMPI to work on Amazon's EC2 but I've been
running into a communications problem. Here is the source (typical
Hello, World):
#include
#include "mpi.h"
int main(argc,argv)
int argc;
char *argv[];
{
int myid, numprocs;
MPI_Init(&argc,&argv);
MPI_Comm_size
