configury: fix git describe with VPATH
configury: fix a typo in config/opal_config_threads.m4
configury: fix pthread flags for fortran
HCOLL:  Fix OMPI to HCOLL predefined datatypes, Ops mapping
OMPI: btl openib: fix max registarable memory caluclation

    - by default allow to register maximum possible (i.e 2 * total_memory)
      memory. This beheviour can be turned off using mca parameter
      "btl_openib_allow_max_memory_registration"

    - In fallback case, use device specific parameters to calulate
      memory limit.
Merge branch 'master' of https://github.com/open-mpi/ompi
coll/libnbc: fix MPI_Ireduce_scatter for single task communicator
when MPI_IN_PLACE is not used.

that commit fixes a regression introduced
open-mpi/ompi@49e79a9ade6c97e357391923f411e75e38fac346
Added several new COMM_TYPE_<> splits

Using the underlying hardware identification to split
communicators based on locality has been enabled using
the MPI_Comm_Split_Type function.

Currently implemented split's are:
  HWTHREAD
  CORE
  L1CACHE
  L2CACHE
  L3CACHE
  SOCKET
  NUMA
  NODE
  BOARD
  HOST
  CU
  CLUSTER

However only NODE is defined in the standard which is why the
remaning splits are referred to using the OMPI_ prefix instead
of the standard MPI_ prefix.

I have tested this using --without-hwloc and --with-hwloc=<path>
which both give the same output.

NOTE: I think something fishy is going on in the locality operators.
In my test-program I couldn't get the correct split on these requests:
  NUMA, SOCKET, L3CACHE
where I suspected a full communicator but only got one.
Fix commit bffb2b7a4bb49c9188d942201b8a8f04872ff63c which broke pmix server functionality
Merge pull request #326 from zerothi/master

Enabled COMM_TYPE_SPLIT dependent on locality