Add support for clock_gettime on Linux. Allow the user to
request a monotonic timer via MCA parameters.
Various cleanups.
Update copyrights and mark ia32 timers as non-monotonic.
ess/alps: add initial alps ess component

Note this alps ess component has nothing to do
with the old CNOS alps component used on
Cray Seastar/Portals3 (Cray XT) systems.

To work properly, changes need to be made to the
open method of the ess/pmi component to keep it
from selecting, and thus initializing, the opal/pmix/cray
component.
orte/common/alps: add an alps common lib to orte

Add an alps common lib to orte.  Add a function
to determine whether or not a process is in a
PAGG container.

Note: we need a better naming convention for
common libs, since right now they use a "flat"
naming convention.
odls/alps: make sure PMI env. variables set up

Add call to orte_odls_alps_get_rdma_creds in the
local proc launch step to obtain the Cray Rdma
credentials from the apshepherd, and to set
the PMI env. variables expected by uGNI BTL, etc.
alps configury changes

Clean up the orte_check_alps.m4.  There was a little of
unnecesary stuff for handling cle 5, since it wasn't actually
doing the right thing, which would be to use pkg-config to
find dependencies both for dynamic and static linking.

Decouple the searching for alps libs, etc. from cray pmi.

Switch the alps ess  and alps odls components' config files
to use the ALPS m4 macro.

alps configury fixes

Improve a check for detecting CLE release.
Improve an error message.
orte/mca/common: add missing Makefile.am
orte/mca/common/alps: fix configure file

Fix configure file for alps to actually check for
alps being available.

Also include stdio.h explicitly in common_alps.c
pmix/cray: remove finalize call from comp close

The finalize call in component close method is
no longer being matched by an equivalent init call,
so remove this call in the close method.
Merge pull request #289 from hppritcha/topic/remove_pmi

Topic/remove pmi
timers: fix 32 bit compile of timer
Merge pull request #295 from jsquyres/topic/bosilca-accurate-timers

Topic/bosilca accurate timers
MPI_Wtime.3: give further explanation about high-res timers
opal_timer_require_monotinic: change to bool / level 5
Fix singleton comm-spawn, yet again. The new grpcomm collectives require a complete knowledge of every active proc in the system in case they participate in a collective. So ensure we pass the required job info when we spawn new daemons, and construct the necessary connections to allow grpcomm to operate.
Fix the clock_gettime monotonic timer. Thanks to Gilles for the
first sketch of the patch.
debuggers: update warning messages when types not found

Fixes #302.
Rename opal_atomic_lifo_t to opal_lifo_t and improve interface

 - Rename opal_atomic_lifo_t to opal_lifo_t to reflect both atomic and
   non-atomic usage. Added new routines (opal_lifo_*_st) for non-atomic
   usage as well as routines conditioned off opal_using_threads(). The
   atomic versions are always thread safe and the non-atomic are always
   not thread safe.

 - Add a new atomic lifo implementation that makes use of 128-bit
   compare-and-swap. The new implementation should scale better with
   larger numbers of threads.

 - Add threading unit test for opal_lifo_t.
Add opal_fifo_t class

This commit adds a new class: opal_fifo.h. The new class has atomic, non-atomic,
and opal_using_threads() conditoned routines. It should be used when first-in
first-out is required and should perform much better than using locks and an
opal_list_t. Like with opal_lifo_t there are two versions of the atomic
implementation: 128-bit compare-and-swap, and spin-locked. More implementations
can be added later (LL/SC comes to mind).

This commit also adds a unit test for the opal_fifo_t class. This test verifies
the fifo implementation when using multiple threads.