Simple, because the test that eventually segfaults only runs if ompi is
configured with threading. Otherwise it is a no-op.
Tim
Jeff Squyres wrote:
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:4
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)
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
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.
