Fixes #3436: Move MPI_Type_create_f90_real fix to v1.7

---svn-pre-commit-ignore-below---

r27707 [[BR]]
Fix the issues with the MPI_Op and the Fortran90 types.

Fixes #3389: Move r27561 to v1.7 branch (retain full FQDN hostnames)

---svn-pre-commit-ignore-below---

r27561 [[BR]]
If the nodename is an IP address, we need to retain the full name (even if keep_fqdn is false) so that the ssh tree spawn can proceed.

cmr:v1.7


r27583 [[BR]]
Add a function to test if a string is in the form of an IP address - doesn't test for validity of the address

r27586 [[BR]]
Strip the domain info from the hostname if that option is specified, protecting IP address-based names

r27618 [[BR]]
Add a function to return the aliases (based on IP addrs) for the current node

r27619 [[BR]]
Add an MCA param to retain all aliases based on IP addrs for node names so that procs can look them up by interface, if desired. If the param is set, pass aliases around to all daemons and procs for local use

r27620 [[BR]]
Per Jeff's suggestion, set the default answer when asking for IP aliases in case we don't find any

Changes to VT:
- configure: pass the MPI configure options (e.g. --with-mpi-lib, --with-mpi-inc-dir) to the OTF configure, even if MPI compiler wrappers were found

Fix the issues with the MPI_Op and the Fortran90 types.

Fixes #3422: Move wrapper compiler fix to v1.7

---svn-pre-commit-ignore-below---

r27662 [[BR]]
Per discussion at the Open MPI developer meeting last week:

1. Restore libopen-pal.la, libopen-rte.la, and libmpi.la to be
separate entities (i.e., don't have libopen-rte.la include
libopen-pal.la, and don't have libmpi.la include libopen-pal.la).
Yay!
1. Consequently, make the wrapper compilers look for flags indicating
that the user wants to compile statically (currently: -static,
!--static, -Bstatic, and "-Wl," in front of all of those). If it
is, follow a 6-way matrix for determinining which libraries to
list on the underlying command line.
1. To support that, add the name of a token static and dynamic
library to look for in each of the wrapper compiler data files.
1. Fix a long-standing typo in the opalcc wrapper data file.


r27667 [[BR]]
If a user supplies both (some form of --static) and (some form of
--dynamic), use the one that was farthest to the right on the command
line.

r27668 [[BR]]
Temporarily revert r27662 and r27667 because something wonky is
happening on OS X. Grumble...

r27670 [[BR]]
Put back the static-library-detection stuff from r27668, with some
additional functionality. Rationale (refs #3422):

* Normal MPI applications only ever use the MPI API. Hence, -lmpi is
sufficient (they'll never directly call ORTE or OPAL
functions). This is arguably the most common case.
* That being said, we do have some test programs (e.g., those in
orte/test/mpi) that call MPI functions but also call ORTE/OPAL
functions. I've also written the occasional MPI test program that
calls opal_output, for example (there even might be a few tests in
the IBM test suite that directly call ORTE/OPAL functions).
* Even though this is not a common case, these applications should
also compile/link with mpicc.
* So we should add a --openmpi:linkall option that will also link
in whatever is necessary to call ORTE/OPAL functions
* Yes, we could hard-code "-lopen-rte -lopen-pal" in Makefiles, but
we do reserve the right to change those library names and/or add
others someday, so it's better to abstract out the names and let
the wrapper supply whatever is necessary.
* ORTE programs, however, are different. They almost always call OPAL
functions (e.g., if they want to send a message, they must use the
OPAL DSS). As such, it seems like the ORTE programs should always
link in OPAL.

Therefore:

* Add undocumented --openmpi:linkall flag to the wrapper compilers.
See the comment in opal_wrapper.c for an explanation of what it
does. This flag is only intended for Open MPI developers -- not
end users. That's why it's undocumented.
* Update orte/test/mpi/Makefile.am to add --openmpi:linkall
* Make ortecc/ortec++'s wrapper data text files always explicitly
link in libopen-pal

r27672 [[BR]]
Refs #3422

* Add some comments in the *-wrapper-data-txt.in files just so that
someone doesn't forget in the future why we link in what we do in
the MPI and ORTE wrapper compilers.
* Update ompi_wrapper_script.in to match the new behavior.
* Update orte_wrapper_script.in to support --openmpi:linkall (which
is a no-op in this case)

Add float and struct timeval fields to the opal_value_t object, and provide dss support for those data types

Fixes #3403: Move r27604 to v1.7 branch (require C99 compiler)

---svn-pre-commit-ignore-below---

r27604 [[BR]]
Per discussion we will now require a C99 compiant compiler.

This change will enable the use of C99 features in Open MPI; subobject naming, restricted pointers, etc.

cmr:v1.7


r27625 [[BR]]
do not include c99 flag in compiler wrappers

Fixes #3425: Move Fortran GET_PROCESSOR_NAME fix to v1.7

---svn-pre-commit-ignore-below---

r27669 [[BR]]
Ensure to set Fortran ierr properly at the end of
MPI_Get_processor_name. Thanks to LANL for spotting the issue.

Fixes #3431: Move r27680 to v1.7 branch

---svn-pre-commit-ignore-below---

r27680 [[BR]]
Remove debug printfs.

cmr:v1.7

Fixes #3383: Move r27557 to v1.7 branch

---svn-pre-commit-ignore-below---

r27557 [[BR]]
Switched FCA collectives component from dlopen to compile-time linking to libfca