The problem is that I am building my entire MPI-based simulator with openmpi
wrappers and my simulator code only compiles with gcc-2.95.3...any
thought??does openmpi NOT work with 2.95.3??
--- On Wed, 9/24/08, Terry Frankcombe wrote:
From: Terry Frankcombe
Both of those are really ancient. Fortran in particular will not work
happily with those. Why don't you install something from the current
epoch? I run happily with gcc 4.3.2.
On Wed, 2008-09-24 at 08:36 -0700, Shafagh Jafer wrote:
> which gcc is prefered to compile openmpi with?? gcc-2.95.3
Hello.
I have a user running a Fortran code that can be built and run on on
both 32-bit and 64-bit architectures. When this code is built for the
x86-64 machines in our cluster, running on OMPI 1.2.7, it runs fine.
However, if we build and run it on 32-bit x86 machines, also running the
same
Thank you. I was able to make everything work by using
orte_launch_agent and bash's $@ to pass the necessary parameters to
orted within my shell script.
I needed to add additional paths to my LD_LIBRARY_PATH/PATH variables
for other necessary libraries, which is why I was pushing on the
Yes - you don't want to use orte_launch_agent at all for that purpose.
What you need to set is an info_key in your comm_spawn command for
"ompi_prefix", with the value set to the install path. The ssh
launcher will assemble the launch cmd using that info.
Ralph
On Sep 24, 2008, at 1:28
Yes, your first sentence is correct. I intend to use the unmodified
orted, but I need to set up the unix environment after the ssh has
completed but before orted is executed.
In particular, one of the more important tasks for me to do after ssh
connects is to set LD_LIBRARY_PATH and PATH to
Sorry for the miscommunication: The processes are started by my
program with MPI_Comm_spawn, so there was no mpirun involved.
If you can suggest a test program I can use with mpirun to validate my
openmpi environment and install, that would probably produce the
output you would like to see.
But
Afraid I am confused. This was the entire output from the job?? If so,
then that means mpirun itself wasn't able to find a launch environment
it could use, so you never got to the point of actually launching an
orted.
Do you have ssh in your path? My best immediate guess is that you
That was the output with plm_base_verbose set to 99 - it's the same
output with 1.
Yes, I'd like to use ssh.
orted wasn't starting properly with orte_launch_agent (which was
needed because my environment on the target machine wasn't set up), so
that's why I thought I would try it directly on the
Could you rerun that with -mca plm_base_verbose 1? What environment
are you in - I assume rsh/ssh?
I would like to see the cmd line being used to launch the orted. What
this indicates is that we are not getting the cmd line correct. Could
just be that some patch in the trunk didn't get
I use SVN checkout. I have invoked :
shell$ svn co http://svn.open-mpi.org/svn/ompi/trunk ompi
I have reinstalled openmpi today.
2008/9/22 Jeff Squyres
> Exactly what version of Open MPI are you using? You mentioned "1.3" -- did
> you download a nightly tarball at some
I compiled it with 2.95.3 and I tested the hello_c and ring_c example and they
seemed fine. So I guess it worked with 2.95.3, am I right??
--- On Wed, 9/24/08, Jeff Squyres wrote:
From: Jeff Squyres
Subject: Re: [OMPI users] which gcc to compile openmpi
No , I do not have any ethernet device aliases.
Thank you,
Sofia
- Original Message -
From: "Jeff Squyres"
To: "Open MPI Users"
Sent: Wednesday, September 24, 2008 2:33 PM
Subject: Re: [OMPI users] Problem with MPI_Send and MPI_Recv
You
I don't think we've tested with 2.95 (that's ancient). I'm pretty
sure we've tested with various versions of the 3 series.
Unless you have a really good reason, you should probably prefer the
newer compiler (IMHO).
On Sep 24, 2008, at 11:46 AM, Brock Palen wrote:
Those are really old
I'm trying to use MPI_Comm_Spawn with MPI_Info's host key to spawn
processes from a process not started with mpirun. This works with the
host key set to the localhost's hostname, but it does not work when I
use other hosts.
I'm using version 1.3a1r19602. I need to use orte_launch_agent to set
Those are really old compilers. I think 3.2 might work, 3.4 works I
know for sure, as well as 4.x+
Brock Palen
www.umich.edu/~brockp
Center for Advanced Computing
bro...@umich.edu
(734)936-1985
On Sep 24, 2008, at 11:36 AM, Shafagh Jafer wrote:
which gcc is prefered to compile openmpi
On Sep 24, 2008, at 10:47 AM, Shafagh Jafer wrote:
Yes, I am using the wrapper compilers. But in my simulator
Makefile.common I am including the files from gcc and g++. Please
see my attached makefile. I am also attaching my previouse
Makefile.common which I was MPICH instead of openmpi.
which gcc is prefered to compile openmpi with?? gcc-2.95.3 or gcc-3.2.3 ???
Yes, I am using the wrapper compilers. But in my simulator Makefile.common I am
including the files from gcc and g++. Please see my attached makefile. I am
also attaching my previouse Makefile.common which I was MPICH instead of
openmpi. Please see both of them and see the defferences, you will
I works find with konsole.
Thank you for the advise.
Thomas.
Samuel Sarholz wrote:
Hi,
I think the problem is that xterm (probably) has the userid bit set
and thus deletes the LD_LIBRARY_PATH.
Try setting the path again before you start gdb, e.g:
mpirun -n 2 -x DISPLAY=:0.0 xterm -e
You don't happen to have ethernet device aliases on either of these
machines, do you?
(we have a problem with this on the trunk/v1.3 series right now; we
were under the impression that it was working fine in the v1.2 series
-- but I figured I'd ask...)
On Sep 24, 2008, at 3:22 AM, Sofia
On Sep 24, 2008, at 12:15 AM, Shafagh Jafer wrote:
Ok now after i have made sure that my code acutally goes and
includes the mpi.h from openmpi and not mpich, now I get really
wierd errors. Below I will paste my mpic++ configurations from --
showme and the errors i gert from running my
Hi,
I'm trying to use gdb and xterm with open mpi on my computer (Ubuntu 8.04).
When I run an application without gdb on my computer in works find but
if I try to use gdb in xterm I get the following error:
mpirun -n 2 -x DISPLAY=:0.0 xterm -e gdb ./ring.out
(gdb) run
Starting program:
Hi Josh!
I believe this is now fixed in the trunk. I was able to reproduce
with the current trunk and committed a fix a few minutes ago in
r19601. So the fix should be in tonight's tarball (or you can grab it
from SVN). I've made a request to have the patch applied to v1.3, but
that may take a
Hello Terry,
I obtain the hostnames of both computers:
pichurra
hpl1-linux
Thank you.
Sofia
- Original Message -
From: "Terry Dontje"
To:
Sent: Tuesday, September 23, 2008 6:24 PM
Subject: Re: [OMPI users] Problem with MPI_Send and
Ok now after i have made sure that my code acutally goes and includes the mpi.h
from openmpi and not mpich, now I get really wierd errors. Below I will paste
my mpic++ configurations from --showme and the errors i gert from running my
code.
[sjafer@DeepThought
26 matches
Mail list logo