1
1
Brian Barrett 70b154f7ff oshmem: Update config code to match OMPI usage
enable_oshmem holds the result of a customer decision and, like
most user options, can have the values "yes" (user wants us to
build feature), "no" (user wants us not to build feature),
"" (user wants us to figure it out), and "<something>" (user
wants us to build feature, with <something> turned on).

This change updates oshmem to not lose this data by not overwriting
enable_oshmem with a yes/no and leaving the original customer
intent in place.  Aside from fixing one bug (below) there are no
customer visible changes in this patch, but it makes it possible
to do the right thing in the upcoming work to allow oshmem to be
disabled based on test results.

There was a cosmetic bug in the existing code where specifying
a feature argument (like --enable-oshmem=awesome) would result
in the "checking if want oshmem" test reporting no, but oshmem
being built anyway.  With this cleanup, the "checking if want
oshmem" test, the final output summary, and what actually happens
will all match.

Signed-off-by: Brian Barrett <bbarrett@amazon.com>
2018-05-25 08:48:50 -07:00
..
2014-08-25 04:41:56 +00:00
2015-04-27 06:50:40 -07:00
2018-04-09 11:45:58 -04:00
2018-04-09 11:45:58 -04:00
2018-04-09 11:45:58 -04:00
2018-04-09 11:45:58 -04:00
2018-04-09 11:45:58 -04:00
2018-04-09 11:45:58 -04:00
2018-04-09 11:45:58 -04:00
2018-04-09 11:45:58 -04:00
2018-04-09 11:45:58 -04:00
2018-04-09 11:45:58 -04:00
2017-09-18 07:30:47 -07:00
2018-04-09 11:45:58 -04:00