Totally insane ... but I was not talking about your rationale. ^^
How did we ended up with the following situation:
-libmca_common_sm_so_version=1:0:0
-libmca_common_mx_so_version=0:0:0
+libmca_common_sm_so_version=2:0:0
+libmca_common_mx_so_version=1:0:0
Where the same type of component (common
On Jun 7, 2010, at 19:47 , Jeff Squyres wrote:
> I'm getting these warnings from PGI 7.0.7. Do they matter? Is "clobber"
> important?
clobber might be the most important piece of information there, it trigger a
warning for the compiler that the condition code register have been altered.
Thi
I'm getting these warnings from PGI 7.0.7. Do they matter? Is "clobber"
important?
CXXmpicxx.lo
"../../../opal/include/opal/sys/amd64/atomic.h", line 91: warning: "cc"
clobber ignored
: "memory", "cc");
^
"../../../o
Sure - just configure with --enable-mca-no-build=filem-rsh,ess-singleton
That will avoid building either of those.
On Jun 6, 2010, at 9:46 PM, 张晶 wrote:
> I find the calls to fork/exec in the orte/mca/ess/singleton and
> orte/mca/filem/rsh. Since the rsh is the only componentfor the filem,
> I
Hi all
A recent update of the libevent seems to cause a regression on our side.
On my 32 cpus node cluster , process launch by srun, hang on
opal_event_loop().
We see a deadlock in MPI_Init (endlessly looping in opal_event_loop())
when we launch processes with pure srun on 32 cores nodes.
He
