I'm unaware of a use case for --without-threads. Does anyone have one?
If not, then I think removing all that dead code would be a Good Thing. On Sep 18, 2014, at 7:03 AM, Gilles Gouaillardet <gilles.gouaillar...@iferc.org> wrote: > Folks, > > for both trunk and v1.8 branch, configure takes the --with-threads option. > valid usages are > --with-threads, --with-threads=yes, --with-threads=posix and > --with-threads=no > > /* v1.6 used to support the --with-threads=solaris */ > > if we try to configure with --with-threads=no, this will result in a > fatal error : > > checking for working POSIX threads package... yes > checking for type of thread support... none > configure: error: User requested MPI threads, but no threading model > supported > > bottom line, the --with-threads configure option is useless in both v1.8 > and trunk. > > is there any plan to support --with-threads=no in the future ? > if no, i'd like to simply remove the --with-threads option > > Thanks in advance for your feedback > > Gilles > > FYI > there is still some dead code / bug related to solaris threads, and this > will be removed / fixed > see https://svn.open-mpi.org/trac/ompi/ticket/4911 > > _______________________________________________ > 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/09/15865.php -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
