Add in 2 patches to fix Libtool <=2.2.6b support for the PGI 10

compiler.

Note that using the name "pgfortran" does not work -- you must still
use the names pgf77 and pgf90.  LT has not yet been fully patched to
support the name "pgfortran".  I advised PGI to take this issue up
with the Libtool guys.

There's still something wrong with the C++ support, however; I get
errors about a template directory switch when compiling the C++ MPI
bindings (doesn't happen with PGI 9.0).  Still working on this... it
feels like it's still a Libtool issue because OMPI is not putting in
this compiler flag as far as I can tell:

{{{
/bin/sh ../../../libtool --tag=CXX   --mode=link pgCC  -g -version-info 0:0:0 -export-dynamic   -o libmpi_cxx.la -rpath /home/jsquyres/bogus/lib mpicxx.lo intercepts.lo comm.lo datatype.lo win.lo file.lo ../../../ompi/libmpi.la -lnsl -lutil  -lpthread
libtool: link: tpldir=Template.dir
libtool: link:  rm -rf Template.dir
libtool: link:  pgCC --prelink_objects --instantiation_dir Template.dir   .libs/mpicxx.o .libs/intercepts.o .libs/comm.o .libs/datatype.o .libs/win.o .libs/file.o   -Wl,--rpath -Wl,/users/jsquyres/svn/ompi-1.3/ompi/.libs -Wl,--rpath -Wl,/users/jsquyres/svn/ompi-1.3/orte/.libs -Wl,--rpath -Wl,/users/jsquyres/svn/ompi-1.3/opal/.libs -Wl,--rpath -Wl,/home/jsquyres/bogus/lib -L/users/jsquyres/svn/ompi-1.3/orte/.libs -L/users/jsquyres/svn/ompi-1.3/opal/.libs ../../../ompi/.libs/libmpi.so /users/jsquyres/svn/ompi-1.3/orte/.libs/libopen-rte.so /users/jsquyres/svn/ompi-1.3/opal/.libs/libopen-pal.so -ldl -lnsl -lutil -lpthread  
pgCC-Error-Unknown switch: --instantiation_dir
make: *** [libmpi_cxx.la] Error 1
}}}

Refs trac:2114.

This commit was SVN r22273.

The following Trac tickets were found above:
  Ticket 2114 --> https://svn.open-mpi.org/trac/ompi/ticket/2114

autogen.sh

@@ -597,6 +597,32 @@ EOF
     run_and_check $ompi_autoconf
 
     run_and_check $ompi_automake --foreign -a --copy --include-deps
+
+    # Ugh.  LT <=2.2.6b need to be patched for the PGI 10.0 fortran
+    # compiler name (pgfortran).  The following comes from the
+    # upstream LT patch:
+    # http://lists.gnu.org/archive/html/libtool-patches/2009-11/msg00012.html.
+    # Note that that patch is part of Libtool (which is not in this
+    # OMPI source tree); we can't fix it.  So all we can do is patch
+    # the resulting configure script.  :-(
+    echo "  ++ Patching configure for Libtool PGI 10 fortran compiler name"
+    rm -f configure.patched
+    cp configure configure.org
+    sed -e 's/gfortran g95 xlf95 f95 fort ifort ifc efc pgf95 lf95 ftn/gfortran g95 xlf95 f95 fort ifort ifc efc pgfortran pgf95 lf95 ftn/' configure > configure.patched
+    cp configure.patched configure
+    rm -f configure.patched
+
+    # Similar issue as above -- the PGI 10 version number broke <=LT
+    # 2.2.6b's version number checking regexps.  Again, we can't fix
+    # the Libtool install; all we can do is patch the resulting
+    # configure script.  :-( The following comes from the upstream
+    # patch:
+    # http://lists.gnu.org/archive/html/libtool-patches/2009-11/msg00016.html
+    echo "  ++ Patching configure for Libtool PGI version number regexps"
+    rm -f configure.patched
+    sed -e 's/\*pgCC\\ \[1-5\]\* | \*pgcpp\\ \[1-5\]\*/*pgCC\\ [1-5]\.* | *pgcpp\\ [1-5]\.*/' configure > configure.patched
+    cp configure.patched configure
+    rm -f configure.patched
 }