Using openmpi-1.0.1. attemping to launch programs via 'mpirun --mca
pls_rsh_agent ssh' fails if the user login shell is tcsh, and
LD_LIBRARY_PATH is unset at startup.
if ($?FOO) setenv BAR $FOO
is an error in tcsh if $FOO is unset, because it expands the whole
line at once. Instead one has t
On Jan 17, 2006, at 3:17 AM, Yves Reymen wrote:
Brian Barrett wrote:
On Jan 16, 2006, at 11:32 AM, Yves Reymen wrote:
Recently openmpi v1.0.1 was installed on our cluster. It contains
all
parameters of ompi_config.h within a #ifndef OMPI_CONFIG_H. I am
wondering how it is possible to give o
David --
Many thanks for this; I learned some new RPM tricks in here. :-)
I love the "--with ..." interface. The only thing that concerns me
is the scalability -- we have to add two things for each --with/--
enable option that we have for configure. Granted, we probably won't
be adding t
Interesting. Since I submitted the report below, I tried installing
v1.01 on my powerbook which also had 10.4.3, the same compiler
versions etc. On the powerbook, ./configure --> make --> make install
worked brilliantly. I began exploring what could be different on the
2 machines. I checked the ve
To follow up for the web archives:
Chris helped us out by tracking down the problem to bad command line
parsing in mpirun (a.k.a. orterun) and submitted a patch to fix it.
I've committed the fix on both the trunk and and the v1.0 branch.
I'll make a 1.0.2a4 shortly that contains this (and
Hi Jean,
I will be looking at this a bit later today, I don't want you to think
we are ignoring you ;-)
Thanks,
Galen
On Jan 18, 2006, at 2:41 PM, Jean-Christophe Hugly wrote:
More info.
Environment of remotely exec'ed progs (by running mpirun ... env):
===
