I think another important question is: why is this related to
threads? (i.e., why does it work in non-threaded builds)
On Mar 4, 2008, at 9:44 AM, Ralph H Castain wrote:
Carto select failing if it doesn't find any modules was called out
in an
earlier message (might have been a commit log) when we set an mca-no-
build
flag on that framework. This should probably be fixed - there are
times when
someone may not wish to build any carto modules.
Is there some reason why carto absolutely must find a module? Can we
crate a
default "none available" module in the base?
On 3/4/08 7:39 AM, "Tim Prins" <tpr...@cs.indiana.edu> wrote:
Hi,
We have been having a problem lately with our MTT runs where make
check
would fail when mpi threads were enabled.
Turns out the problem is that opal_init now calls
opal_base_carto_select, which cannot find any carto modules since we
have not done an install yet. So it returns a failure. This causes
opal_init to abort before initializing the event engine. So when we
try
to do the threading tests, the event engine is uninitialized and
fails.
So this is why it fails, but I do not know how best to fix it. Any
suggestions would be appreciated.
Tim
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
--
Jeff Squyres
Cisco Systems
