Hi Jeff,
Thanks.
I tried as what you suggested. Here are the output:
>>>
yiguang@gulftown testdmp]$ ./test.bash
[gulftown:25052] mca: base: components_open: Looking for plm
components
[gulftown:25052] mca: base: components_open: opening plm
components
[gulftown:25052] mca: base: components_ope
Hi Jeff,
Here I made a developer build, and then got the following message
with plm_base_verbose:
>>>
[gulftown:28340] mca: base: components_open: Looking for plm
components
[gulftown:28340] mca: base: components_open: opening plm
components
[gulftown:28340] mca: base: components_open: found l
Hi Ralph,
Thanks, here is what I did as suggested by Jeff:
> What did this command line look like? Can you provide the configure line as
> well?
As in my previous post, the script as following:
(1) debug messages:
>>>
yiguang@gulftown testdmp]$ ./test.bash
[gulftown:28340] mca: base: componen
> Actually, I should say that I discovered that if you put --prefix on each
> line of the app context file, then the first
> case (running the app context file) works fine; it adheres to the --prefix
> behavior.
Yes, I confirmed this on our cluster. It works with --prefix on each line of
the
Hi Jeff, Ralph--
Please let me follow the thread, here are what I observed:
(All with the same test script test.bash I post in my previous emails, so run
with app file fed to mpirun command.)
(1) If I put the --prefix in the app file, on each line of it, it works fine as
Jeff said.
(2) Since
It turns out that the "-x" option should be put on each line of the app file if
app file is used.
OK, now test results on our cluster, in case this may be useful to some Open
MPI users(Open MPI 1.4.3 used on
my system):
(1) If I run mpirun command from command line as Jeff's foo test, everythi
