the problem is that now the behavior is changed. Before: user provided single flag and could use MT support. Now same method will not work starting from v1.8.4 which is production branch and will live for a long time with it.
Is that possible that some1 familiar with this configure kung-fu will fix it to keep old behave by enabling both flags if one of them is ON? Thanks On Wed, Nov 5, 2014 at 5:41 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> wrote: > On Nov 5, 2014, at 9:42 AM, Mike Dubman <mi...@dev.mellanox.co.il> wrote: > > > Hey Jeff, > > > > now we use only this "--enable-mpi-thread-multiple" and it worked. > > does it mean that now we need to pass "--enable-mpi-thread-multiple > --enable-opal-multi-threads" to get it working again? > > Maybe if one of the params used it should enable another one as well? > > I believe that that is the case. > > Keep in mind: this mess is cleaned up on the trunk; the threading options > are simpler. This is "legacy" now, on the v1.8 branch, and likely won't be > updated. > > The change that happened recently was that THREAD_MULTIPLE support was > accidentally enabled by default on the v1.8 branch (which wasn't > intended). The change a few days ago was to turn THREAD_MULTIPLE support > off by default. > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2014/11/16200.php > -- Kind Regards, M.
