Per Geoffroy Vallee, use the OPAL constant
Ahem....cleanup a copy/paste error in naming of these functions
Fix --without-hwloc
Add a function to return the kernel index of the corresponding interface from an IPv4/6 string or hostname
As initially reported by Eric Chamberland in
http://www.open-mpi.org/community/lists/users/2013/04/21689.php, the
assert in opal_datatype_is_contiguous_memory_layout() is not always
correct -- he supplied a test case where it was not valid,
essentially:

 1. Call MPI_Type_create_indexed_block(0, ..., &newtype) and commit newtype
 1. Call MPI_Type_create_resized(newtype, 0, nonzero_value, &resized) and commit resized
 1. Call MPI_File_set_view with resized

This will eventually call opal_datatype_is_contiguous_memory_layout(),
and the assert will fail.  After some consultation with George, it was
determined that the assert() is basically good, but it needs to also
check for (count != 0).
Remove unused variables.
If there are no BTLs, do ''not'' actually shut down the fd listener,
because a) it may still be needed to shut down the CPCs, and b) it
will be shut down during component_close().
Use some handy shell scripts from W Spector to s/ierr/ierror/ in the
mpi module.
Remove and ignore build products
Add missing include
Update platform files
Fix an obvious typo - it was set to default to true when instantiated.
Fix minor typo
Add the ability to use an external version of libevent. Clearly not recommended at this time. I've verified that it works in limited scenarios, but more thorough testing and performance impacts need to be assessed.

Interesting how many includes had to be fixed here and there to fill in missing dependencies :-)
Update ignores and remove build product
btl/openib: fix typo
Fix BTL_VERBOSE - when the MCA param change was committed, it left the base verbosity variable declared so things compiled. Sadly, the verbosity was now being set to a new variable, so debug never was output.
vprotocol: remove the old output and use the framework output
Revert r28417 - given the non-standard way vprotocol is implemented, I see no way to use the framework verbosity here. Best to just leave it alone as those who use it know what they need to do to get debug output
Fix typo in check for mpi_leave_pinned vs mpi_leave_pinned_pipeline.