Open MPI 1.2.3 is out the door... up the branch's version to start work on .4
Closes #1053: Remove sysfs check for openib BTL

Submitted by jsquyres, Reviewed by gleb, RM-Approved by tdd

Patch applied corresponding to r14971:
libsysfs headers are required for libibverbs v1.0 (i.e., OFED 1.0 and
OFED 1.1), meaning that <infiniband/verbs.h> would #include
<sysfs/libsysfs.h>.  Hence, if the libsysfs headers did not exist on a
system, including <verbs.h> would fail.

With older versions of Autoconf, we would simply test for the
''presence'' of the <infinband/verbs.h> and not actually try to
''use'' it.  This could leave OMPI in a weird situation on systems
that did not have the sysfs headers installed: configure would
complete successfully, but the build of the openib btl would fail.
Some users complained, thinking that there was a real compile error in
the OMPI code base.

Hence, we decided that it would be better to AC_CHECK_HEADER for the
sysfs header files in configure.  If the sysfs header files were not
found, configure would abort.  Users generally understand when
configure aborts, and know how to read the output and fix the
underlying problem; it was ''much'' more obvious than having the OMPI
build fail for nebulous reasons much later.

Note that we also checked for / added -lsysfs, but that wasn't
necessary because libibverbs already run-time linked to it (i.e.,
libibverbs couldn't have been installed if the sysfs libraries weren't
installed).

However, there are now two reasons why the check for sysfs's header
files is no longer necessary:

 * Newer versions of Autoconf are now used for OMPI tarballs that
  check for both the presence '''and''' usability of header files.
  Hence, AC_CHECK_HEADER for <infiniband/verbs.h> will actually try
  to ''use'' it, so if the sysfs header files are not installed,
  AC_CHECK_HEADER will (rightfully) fail.
 * libibverbs v1.1 (i.e., OFED 1.2 and beyond) does not require
  libsysfs at all (headers or libraries).

When checking for the sysfs header files, OMPI's configure ''forces''
you to have sysfs installed, even though it may not be needed (e.g.,
libibverbs v1.1 and beyond).  Clearly, this is not good (especially
since the sysfs software package is now deprecated, and some Linux
distros no longer install it by default).

So this commit simply removes the check for the sysfs header files and
libraries, allowing OMPI to be build on systems with libibverbs >=1.1 that
do not have sysfs installed.

For systems with libibverbs 1.0, if they do not have the sysfs headers
installed, we'll still fail AC_CHECK_HEADER and therefore still fail
configure properly.  I expanded the warning message to say that if
libibverbs 1.0 is being used, check to ensure that sysfs is installed,
yadda yadda yadda.
Closes #1074: localhost OOB fixes

Submitted by Brian, Reviewed by Jeff, RM-Aproved by tdd

Patch "v1.2-oob-dev-2.diff" applied:
The patch fixes a couple of segfault and failures that can 
occur when specifying devices for use by the OOB (Refs #1059).
Closes #1077: openib ConnectX HCA tunings

Submitted by pasha, Reviewed by Jeff, RM-Approved by tdd

r14639: Add definitions for Hermon/ConnectX Mellanox HCA

r14705: Adding new vendor_part_id for Mellanox Hermon HCA
Closes #1082: Move HCA params HP addition to release branch

Submitted by Jeff, Reviewed by Pasha, RM-Approved by tdd

r15316:
Update the vendor ID list to include HP (0x1708).
Thanks to Peter Kjellstrom for pointing this out.
Closes #1061: rsh $SHELL fixes

Submitted by Jeff, Reviewed by Rainer Keller, RM-Approved by tdd.

patch applied which cooresponds to r15156:
Per suggestion, if we don't find a valid shell via getpwuid(), also 
check the $SHELL environment variable. Also perform a few minor 
cleanups along the way.
Closes #1078: ROMIO non-blocking error reporting fix

Submitted by Brian, Reviewed by Jeff, RM-Approved by tdd

r15296:
Fix situation where we were not propogating error codes from
ROMIO into non-blocking request status fields, so it was never
being relayed to the user.
Closes #1070: Allow bproc operations on the head node if it was allocated

Submitted by rhc, Reviwed by Brian, RM-Approved by tdd.

r15232:
Allow bproc operations on the head node if it was allocated for our use.
Closes #1069: SM BTL large -np SEGV fix

Fixed by Gleb, Reviewed by paklui, RM-Approved by tdd

Patch applied which corresponds to r14119:
Initialize fifos at SM BTL init time instead of waiting for
first send. This waist slightly more memory, but prevents
problem when fifo cannot be allocated later during a job run
when memory resource is exhausted.
Closes #974: Make udapl btl utilize rdma capabilities

Submitted by dkerr, Reviewed by various, RM-Approved by tdd

Changes applied corresponding to these changesets plus
the patch.974 included on the ticket:

r13082: add udapl rdma capabilities into the udapl btl

r13090: fix for bug #749, though I can not confirm without a linux compiler

r13971: Fix warnings when building with UDAPL - minor formatting errors.

r14493: move mca parameter registration into own .c and .h files

r14511:
change so that we only check connection queue when expecting
a connection; create a mca parameter that controls frequency
at which the async queue is checked

r14634:
latency improvements: use ompi_free_list_init_ex, create optimal
alignment parameter, remove rdma guarantee path, replace
dat_lmt_sync_rdma with use of volatile

r14659:
break evd_qlen into individual qlens (async,dto,conn);
add checks based on udapl limits and number of peers

r14678:
add user warning message to inform when udapl btl is no longer
able to register memory

r14691: clean up compile warnings

r14692: remove an assignment which is not required

r14792: 
don't call dat_evd_resize if new value is less than or equal
to current because ofed stack does not return DAT_INVALID_STATE

r14878: add support for connection private data, off by default

r15362: improve message to user when dat_ia_open fails
Resync the NEWS file with the trunk, and bump the greek VERSION to b0.
Closes #1075: openib parameter checking fixes

Submitted by pasha, Reviewed by jsquyres and gshipman, RM-Approved by tdd

Patch applied which corresponds to r13936 plus patch from Ticket #1076:
Fix broken IB parameter validation in openib.
Closes #1084: Add support for DDT parallel debugger

Submitted by jsquyres, Reviewed and RM-Approved by tdd

Patch applied corresponding to r15323:
Add support for DDT parallel debugger, which required several things: 
 * Making some symbols and types be global (vs. static) in orterun 
 * Adding a "ddt" entry in the MCA parameter orte_base_user_debugger 
   default value 
 * Add support for @executable@, @executable_argv@, and @single_app@ 
   tokens in the orte_base_user_debugger MCA parameter. 
 * Added various error checks and corresponding help messages after 
   finding a debugger in the PATH
Closes #1090: mpool sm size specification fix

Submitted by paklui, Reviewed by Gleb, RM-Approved by tdd.

r15419:
 * Fixed the mpool sm size specification problem at large -np
   due to variable has overflown.
 * Added a verbose MCA param for showing the actual size of
   the mpool sm allocation.

See trac #1083 for details
Bump the greek VERSION to b1.
Refs #1069: SM BTL large -np SEGV fix

Reverted r15406 due to bad side effects reported by paklui.
Awaiting a different fix.
Updated NEWS file since I reverted CMR #1069...
(I did not revert CMR #1054, I made a bad trunk log entry just a momet ago...)
Closes #1054: IOF fixes

Submitted by jsquyres, Reviewed by Rolf V., RM-Approved by tdd and Rich

Merge performed with:
{{
cd your_v1.2_checkout
svn merge -r 15462:HEAD https://svn.open-mpi.org/svn/ompi/tmp/iof-v1.2-merge .
}}

Which coresponded to these four changesets:

r14967:
A bunch of fixes from the /tmp/iof-fixes branch that fix up ''some''
(but not ''all'') of the problems that we have seen with iof:

 * Reading very large files via stdin redirected to orteun (Sun saw
  this)
 * Reading a little bit of a large file redirected to orterun's stdin
  and then either closing stdin or exiting the process

The Big Change was to make the proxy iof (the one running in non-HNP
orteds) send back a "I'm closing the stream" ACK back to the service
iof.  This tells the HNP that there will be nothing more coming from
that peer, and therefore the iof forward should be removed.

Many other minor cleanups/fixes, terminology changes, and
documentation additions are included in this commit as well.  However,
there are still some pretty big outstanding issues with IOF that are
not addressed either by #967 or this commit.  A few examples:

 * IOF was designed to allow multiple subscribers to a single stream.
  We're not entirely sure that this works (for one thing, there is
  nothing in the ORTE/OMPI code base that uses this functionality).
 * There are also resources leaked when processes/jobs exit (per
  Ralph's first comment on this ticket).
 * There is no feedback to close orterun's stdin when all subscribers
  to the corresponding stream have closed stdin.

r14981:
 * Forgot to update the iof null component when we revamped the IOF
  framework.  Updated pointers to match current definitions.
 * Trimmed some dead wood while I was at it:
  * No need for component close function that does nothing
  * Use BEGIN/END_C_DECLS
  * Use recent MCA param register function
  * Ditch MCA param orte_iof_debug (it wasn't used anywhere)
  * Use MCA param orte_iof_override properly in the code (i.e., look
    up the value once and use the cached value later)

r14984: Fix typo that accidentally always resulted in a "true" result.

r15013:
Fix a warning that Tim P. found. 

The warning was indicative of overly-complex code anyway. So I 
removed the "first" bool and simply use a sentinel value in seq_min to 
indicate that nothing has changed. Note that this is "correct enough" 
for the moment -- more fixes will come in this area with tickets #1049 
and/or #1051.
Resynced the 1.2 NEWS file with the trunk.
Closes #1094: Optional fortran datatype fixes

Submitted by rusraink, Reviewed by George and Jeff, RM-Approved by tdd

r14818:
The optional Fortran datatypes may not be available 
Do not initialize them, if not. 
If initializing them, check for the correct C-equivalent type 
to copy from... 
Issue a warning, when a type (e.g. REAL*16) is not available to 
build the type (here COMPLEX*32). 
This fixes issues with ompi and pacx. 

Works with intel-compiler and FCFLAGS="-i8 -r8" on ia32.