On 30 Oct 2009, at 20:28, Jeff Squyres wrote:
What George is describing is the Right answer, but it may take you
a little time.
FWIW: the complexity of a topo component is actually pretty low.
It's essentially a bunch of glue code (that I can probably mostly
provide) and your mapping al
Good Morning,
i am trying to compile some kind of 3rd party btl module into my
openmpi. I got the 1.3.3 release tarball, and i can now successfully
call autogen.sh, configure and build after downgrading autoconf and
friends to the exact versions suggested on the hacking site (i had the
most r
On Nov 3, 2009, at 3:40 AM, Luigi Scorzato wrote:
This defines the precise relation between ranks and coordinates. Once
I know this, I do not even need to write a topo component, because I
can define the ranks of my computing nodes in a rankfile in order
that they get the coordinates that they n
Hi,
I am using open-mpi version 1.3.2. on SLES 11 machine. I have built it
simply like ./configure => make => make install.
I am facing the following error with mpirun on some machines.
Root # mpirun -np 2 ls
[NO-NAME] ORTE_ERROR_LOG: Not found in file runtime/orte_init_stage1.c at
line 182
Hi,
hm, I did not set any threading related options in configure, so I guess
threading was not disabled.
I compiled it again with the following configure options,
--enable-debug --enable-memchecker --enable-mem-debug --disable-ft-thread
--disable-progress-threads --disable-mpi-threads
and the
On Nov 3, 2009, at 10:02 AM, Mondrian Nuessle wrote:
hm, I did not set any threading related options in configure, so I
guess threading was not disabled.
I compiled it again with the following configure options,
--enable-debug --enable-memchecker --enable-mem-debug --disable-ft-
thread --di
No parameter will help - the issue is that we couldn't find a TCP interface
to use for wiring up the job. First thing you might check is that you have a
TCP interface alive and active - can be the loopback interface, but you need
at least something.
If you do have an interface, then you might rebu
On Nov 3, 2009, at 4:14 AM, Christian Bendele wrote:
i am trying to compile some kind of 3rd party btl module into my
openmpi. I got the 1.3.3 release tarball, and i can now successfully
call autogen.sh, configure and build after downgrading autoconf and
friends to the exact versions suggested o
Avneesh/QLogic just pointed out to me that we have a binary
compatibility issue (he's going to file a blocker ticket shortly).
When we changed the .so version numbers right before 1.3.4rc3, we made
it that apps compiled with 1.3.3 will not run against 1.3.4 because
the apps are dependent u
MTT is finding (and I have confirmed by hand) that 1.3.4 is failing
the mpi_test_suite P2P tests Ring Persistent (15/47). It does not
fail on the trunk. Can someone confirm if this is a real problem?
Here's a snipit of the output:
P2P tests Ring Persistent (15/47), comm MPI_COMM_WORLD (1/1
Hmm. Looks like this fails in 1.3.0 as well. So -- not a
regression. But it still does seem weird. I'll file a ticket for 1.4.
On Nov 3, 2009, at 9:22 PM, Jeff Squyres (jsquyres) wrote:
MTT is finding (and I have confirmed by hand) that 1.3.4 is failing
the mpi_test_suite P2P tests Ring P
Mea culpa. Should be fixed now. If you can please restart the testing
process.
Thanks,
george.
On Nov 3, 2009, at 21:35 , MPI Team wrote:
ERROR: Command returned a non-zero exist status (v1.5):
./configure --enable-dist
Start time: Tue Nov 3 21:30:07 EST 2009
End time: Tue N
12 matches
Mail list logo
