Revert "coll/basic: fix segmentation fault in neighborhood collectives if the degree"

This reverts commit 9c788ff9400960823637dc0eebb3a8640414fa05.
coll/basic: fix segmentation fault in neighborhood collectives if the degree
of the topology is higher than the communicator size

It is possible to have a topology degree higher than the size of the communicator.
For example, a periodic cartesian communicator on MPI_COMM_SELF. This will leave
the neighborhood collectives with a request buffer that is too small.

This commits introduces a semantic change :
from now, c_topo must be set before invoking coll_select
* comment on communicator creation in mca_topo_base_dist_graph_create(...)
* use accesors to retrieve topo info
btl/scif: start the listening thread once only
Merge branch 'master' of https://github.com/open-mpi/ompi
ob1: change an OPAL_UNLIKELY to OPAL_LIKELY

Per
https://github.com/open-mpi/ompi/commit/924d39e415e7df53841803941e450aa42b119650#commitcomment-8378266,
this OPAN_UNLIKELY should really be OPAL_LIKELY.
add new function to pkg.m4 to help static linking

There is a continued interest in being able to do static
linking of executables.  When using pkg-config to determine
linking requirements, the default behavior is to only
specify libraries required for dynamic linking.

In many cases, it suffices even for static linking to
use

pkg-config --libs package

to obtain the linkage string required for ld.  However, for
libraries that have dependencies on non-standard libraries,
this may not be the case.  The cray PMI library is such a case.

On a Cray CLE 5.X system, for example

pkg-config --libs cray-pmi

returns a string like

-L/opt/cray/pmi/5.0.2-1.0000.9906.117.2.ari/lib64 -lpmi

whereas

pkgconfig --static --libs cray-pmi

returns a string (modified for git commits) like

-L/opt/cray/pmi/5.0.2-1.0000.9906.117.2.ari/lib64
-L/opt/cray/ugni/5.0-1.0000.8563.255.10.ari/lib64
-L/opt/cray/alps/6.0.0-2.0000.8544.102.21.ari/lib64
-L/opt/cray/wlm_detect/1.0-1.0000.48964.8.2.ari/lib64
-L/opt/cray/rca/1.0.0-2.0000.49383.133.60.ari/lib64
-lpmi -lpthread -lalpslli -lpthread -lwlm_detect
-lugni -lpthread -lalpsutil -lpthread -lrca

Unfortunately the pkg.m4 does not contain a function for adding
the --static option to PKG_CHECK_MODULES. This commit defines
a new function, PKG_CHECK_MODULES_STATIC, which in addition to
defining the $1_CFLAGS and $1_LIBS variables defined by PKG_CHECK_MODULES,
also defines a $1_STATIC_LIBS.
Add missing parens on values being passed to OPAL_THREAD_ADD32
pkg.m4: "Open MPI", not "OpenMPI" :-)
opal_check_pmi.m4: trivial whitespace cleanup; no code changes
OSHMEM: spml ikrit: disable rdmap op DCI pool

Instead use single pool for both rdma and send receive ops.
OSHMEM: spml ikrit: disable rdmap op DCI pool

Instead use single pool for both rdma and send receive ops.
Merge branch 'master' of github.com:open-mpi/ompi

Conflicts:
	oshmem/mca/spml/ikrit/spml_ikrit_component.c
Don't open PSM context when run on single node

When running many ranks on a single node using PSM, it's possible to
exhaust the network hardware contexts (there are 16).  This patch checks
if only a single node is being used. If so, the 'ipath' component of PSM
is disabled and no hardware contexts are opened.
opal_check_ident.m4: make the test match what we do in the code base

Per #257, the configure test used to check:

```c
```

But out in the code base, we actually do this:

```c
// ...
```

This commit updates the configure test to ```#define``` a string and
then use that with the various ident strategies.

Fixes #257
Update the grpcomm direct component's priority so it sits at the bottom of the list, as it should now that the other components are active. Cleanup up the signature print function a touch to make it more readable. Remove the unneeded xcast functions in brks and rcd components as we will just fall thru to using the "direct" one
Trivial suppression file fix per #216
fix ompi_request_wait vs ompi_request_wait_all and
MPI_STATUS_IGNORE vs MPI_STATUSES_IGNORE
Require -D_REENTRANT flag for both CFLAGS and CPPFLAGS if building under Solaris
Ensure that mpirun correctly selects the HNP ess component without attempting to init the PMI subsystem as mpirun won't be supported anyway, so let's avoid the error message. Also, daemons launched by the plm/slurm component must use the ess/slurm module as we cannot trust the Slurm PMI_Init functions to correctly tell us when PMI support is available.