Temporarily make the direct grpcomm component the default until we can debug the other modules
Fixed offset data type in communication
Fixed offset data type in communication
Fixed offset data type in communication
Fix potential double free in cray pmi cray_fini
Fix bad cut/paste for commit c19e7369
Add support for detecting CUDA managed memory.  Disabled for now.
remove ignored restrct return type qualifier

The use of restrict in the return type qualifier for mca_btl_vader_reserve_fbox
is being ignored by gnu compiler.  for newer gcc, one sees this warning only
with -Wignored-qualifiers set, but for older variants of gcc it was reported
that numerous warning messages about this ignored qualifier were being
generated as vader is being compiled.

The warning reported by gcc is

btl_vader_fbox.h:53:47: warning: type qualifiers ignored on function return type [-Wignored-qualifiers]
 static inline mca_btl_vader_fbox_t * restrict mca_btl_vader_reserve_fbox (struct mca_btl_base_endpoint_t *ep, const size_t size)
Revert r32675 in favor of a different solution proposed by Brice
mca_base_var: fix possibilty of unaligned variable assignments

Add a debugging check that ensures that the registered storage is
aligned appropriately for the type that is specified.

When we know that the storage is properly aligned, we can cast the
mbv_storage to the appropriate type and then simply do the assignment.
We used to do this assignment via a union, but clang's
-fsanitizer=alignment complained about this.
silence a warning regarding the return value of the fbtl's.
it is ok to not have a sharedfp component selected, as long as no
sharedfp functionality is being used. Return an error however if no
sharedfp component is selected and the applications calls a
file_read/write_shared function.
Check for multiple declarations of a given MCA param and error out if detected as that can create an ambiguous definition of the param value.

Refs #4897
Per patch from Samuel Thibault, silence warning from Clang
opal_search_libs.m4: remove redundant AC_MSG_CHECKING/RESULT

The AC_MSG_CHECKING/AC_MSG_RESULT in OPAL_SEARCH_LIBS_CORE were
generating recursive redundant output (i.e., AC_SEARCH_LIBS already
outputs "checking for library containing X... -lY".

Also add the "uppername" logic to OPAL_SEARCH_LIBS_COMPONENT so that
these two macros stay symmetrical.

Refs #4894.
orte_check_lsf.m4: improve the search for LSF libraries

Based on a patch from Joshua Randall, improve the search for LSF
libraries in orte_check_lsf.m4.  This improvement theorhetically
allows the LSF libraries to work in a variety of OSs by properly
searching for its dependent libraries using a variety of library
names.

Fixes #4889.
opal_search_libs: correctly AC_DEFINE results of search

1. It is not sufficient to put the result of m4_toupper() in a
variable and use that variable as the variable name in
AC_DEFINE_UNQUOTED.  Instead, just use m4_toupper() directly in
AC_DEFINE_UNQUOTED.  Also, save the result value in a "permanent"
variable that isn't erased, just in case autoconf decides to be lazy
about instantiating the body AC_DEFINE_UNQUOTED and move it later
(this is probably overkill :-) ).
1. Use the OMPI Way of always defining macros (to 0 or 1).  Then also
slightly change the logic in util/basename.c to just check
OPAL_HAVE_DIRNAME (because it will always be defined).

Refs #4894
plm_rsh_module.c: output to the framework output

Trivial fix from r32686: don't output to stream 0, but rather to
orte_plm_base_framework.framework_output (this is the way it was
before r32686).  In reality, this is going to end up being stream 0,
anyway, but we might as well be pedantically correct...

Refs #4897.
Not sure how we could get to this point without having already detected the error, but just to be safe - check for end-of-array and return if error.

Refs #4897
Merge remote-tracking branch 'ompi/master'