Hi,
I have installed openmpi-1.3. When I checked for the example programs,
the output shows only rank 0 of size 1 for 2 processors. When I gave the
command: *mpirun -hostfile node -np 2 hello_c*
the output is
Hello, world, I am 0 of 1
Hello, world, I am 0 of 1
In my node file, I have
*IP addr
Hi Ramya,
Ramya Narasimhan wrote:
Hi,
I have installed openmpi-1.3. When I checked for the example programs,
the output shows only rank 0 of size 1 for 2 processors. When I gave the
command: *mpirun -hostfile node -np 2 hello_c*
the output is
Hello, world, I am 0 of 1
Hello, world, I am 0
Hi Raymond,
Thanks for your reply. Actually I have installed lam
previously. When I completely removed the mpirun from the /usr/bin and set
mpirun to this openmpi path its working correctly.
Ramya
On Fri, Feb 13, 2009 at 1:47 PM, Raymond Wan wrote:
>
> Hi Ramya,
>
>
> Ramya Nar
Thak you Jeff Squyres,
I've installed Open MPI v1. and now it's OK.
Kind regards,
Jeff Squyres a écrit :
The warning is a side-effect of how we're probing for
OpenFabrics-capable hardware (e.g., IB HCAs). While annoying, the
warning is harmless -- it's just noisily indicating that you seem to
Yes, it was doing no sensible work -
It was only intended to show the error message.
I now downloaded the latest nightly tarball and installed it,
and used your version of the test programm. It works -
*if* is use the entire path to mpirun:
[jody@localhost 3D]$ /opt/openmpi-1.3.1a0r20534/bin/mp
On Feb 13, 2009, at 4:39 AM, jody wrote:
Yes, it was doing no sensible work -
It was only intended to show the error message.
I now downloaded the latest nightly tarball and installed it,
and used your version of the test programm. It works -
*if* is use the entire path to mpirun:
[jody@localh
Forgot to add.
i have /opt/openmpi/bin in my $PATH
I tried around some more and found that it
also works without errors if use
/opt/openmpi/bin/mpirun -np 2 ./sr
I don't understand this, because 'mpirun' alone should be the same thing:
[jody@localhost 3D]$ which mpirun
/opt/openmpi/bin/mpirun
Can you send all the information listed here:
http://www.open-mpi.org/community/help/
On Feb 12, 2009, at 8:48 PM, Ramya Narasimhan wrote:
Hi,
I have entered the IP address of the system in the hosts
file (twice the IP for two CPU's) .I don't know about this mca
parameter.
Well all i do seems to verify that only one version is running:
[jody@localhost 3D]$ ls -ld /opt/openmp*
lrwxrwxrwx 1 root root 26 2009-02-13 14:09 /opt/openmpi ->
/opt/openmpi-1.3.1a0r20534
drwxr-xr-x 7 root root 4096 2009-02-12 22:19 /opt/openmpi-1.3.1a0r20432
drwxr-xr-x 7 root root 4096 2009-
What is your PATH / LD_LIBRARY_PATH when you rsh/ssh to other nodes?
ssh othernode which mpirun
ssh othernode env | grep PATH
On Feb 13, 2009, at 5:11 AM, jody wrote:
Well all i do seems to verify that only one version is running:
[jody@localhost 3D]$ ls -ld /opt/openmp*
lrwxrwxrwx 1 root ro
This was run only locally.
Here at home i only have one computer.
But indeed i hadn't set the $LD_LIBRARY_PATH to /opt/openmpi/lib.
After i did so, the error didn't occur anymore with the short call.
It looks like the libraries to run with were from
/usr/lib/openmpi/1.2.4-gcc/
Apparently i hadn
Hi Everyone,
I'm getting a "/usr/bin/ld: skipping incompatible
/usr/local/lib/libgcc_s.so when searching for -lgcc_s" when compiling
some of the openmpi 1.3 examples. The programs still compile and run.
Does anyone know if this warning is something I should be concerned
about and/or how I c
Hi Gary,
that is a linker warning.
You probably have a libgcc_s.so in 32 and 64 bit. The linker finds the
"wrong" version first and skips it. After that the matching one is
linked and thus your program runs.
So nothing to worry about.
To avoid the warning you can switch the (default) search o
Thanks!, I was thinking is was something like that.
Gary
Samuel Sarholz wrote:
Hi Gary,
that is a linker warning.
You probably have a libgcc_s.so in 32 and 64 bit. The linker finds the
"wrong" version first and skips it. After that the matching one is
linked and thus your program runs.
So n
Sorry for the delay in replying; I was fully occupied by MPI Forum
activities over the past week or so.
It is quite possible that the reason for the multiple tests is OMPI's
lazy wireup scheme. Making an openfabrics connection likely requires
multiple passes down through OMPI's progression
15 matches
Mail list logo