Merge pull request #116 in HDFFV/hdf5 from ~LRKNOX/hdf5_lrk:hdf5_1_8_18 to hdf5_1_8_18

* commit 'b9be12102550f678b4e0cdb179ca560966bbf65c':
  Update Windows tested platforms information.
  Update shared object file numbers according to changes in v1.8.18 release. Update autotools and libtool versions. Run bin/reconfigure.
  Updated RELEASE.txt for C++ API and Packet Table APIs for 1.8.18.
  Updated "Platforms supported" section.
  Clone directly into "current".
  Translate svn co to git clone command. Remove unnecessary references to svn.

1 files changed, 69 insertions, 54 deletions

diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt
index 1b59086..a783fa9 100644
--- a/release_docs/RELEASE.txt
+++ b/release_docs/RELEASE.txt
@@ -168,12 +168,30 @@ Bug Fixes since HDF5-1.8.17
 
     C++ API
     -------
-    - None
+    - The macros H5_NO_NAMESPACE is deprecated from the HDF5 C++ API library.
+      In future releases, the macros H5_NO_STD and OLD_HEADER_FILENAME may
+      also be removed.
+      (BMR, 2016/10/27, HDFFV-9532)
 
 
     High-Level APIs:
     ---------------
-    - None
+
+    Packet Table APIs:
+    ------------------
+    - The high-level API Packet Table (PT) did not write data correctly when
+      the datatype is a compound type that has string type as one of the
+      members.  This problem started in 1.8.15, after the fix of HDFFV-9042
+      was applied, which caused the Packet Table to use native type to access
+      the data.  It should be up to the application to specify whether the
+      buffer to be read into memory in the machine’s native architecture.
+      Thus, the PT is fixed to not use native type but to make a copy of the
+      user's provided datatype during creation or the packet table's datatype
+      during opening.  If an application wishes to use native type to read the
+      data, then the application will request that.  However, the Packet Table
+      doesn't provide a way to specify memory datatype in this release.
+      Please refer to the Known Problems section for a work-around.
+      (BMR, 2016/10/27, HDFFV-9758)
 
 
     Fortran High-Level APIs:
@@ -195,10 +213,10 @@ They are built with the configure process unless specified otherwise.
     (NASA G-ADA)                  xlC/xlC_r 10.1.0.5
                                   xlf90/xlf90_r 12.1.0.6
 
-    Linux 2.6.32-573.3.1.el6    GNU C (gcc), Fortran (gfortran), C++ (g++)
+    Linux 2.6.32-573.22.1.el6     GNU C (gcc), Fortran (gfortran), C++ (g++)
     #1 SMP x86_64 GNU/Linux       compilers:
-    (platypus)                       Version 4.4.7 20120313
-                                     Version 4.8.4, Version 5.2.0
+    (platypus/mayll)              Version 4.4.7 20120313
+                                     Versions 4.8.4, 4.9.3, 5.2.0 
                                   PGI C, Fortran, C++ for 64-bit target on
                                   x86-64;
                                       Version 15.7-0
@@ -207,16 +225,16 @@ They are built with the configure process unless specified otherwise.
                                      Version 15.0.3.187 Build 20150407
                                   MPICH 3.1.4 compiled with GCC 4.9.3
 
-    Linux 2.6.32-504.8.1.el6.ppc64 gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11)
-    #1 SMP ppc64 GNU/Linux        g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11)
-    (ostrich)                     GNU Fortran (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11)
+    Linux 2.6.32-573.18.1.el6     gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)
+    #1 SMP ppc64 GNU/Linux        g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)
+    (ostrich)                     GNU Fortran (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)
                                   IBM XL C/C++ V13.1
                                   IBM XL Fortran V15.1
 
-    Linux 3.10.0-229.14.1.el7   GNU C (gcc), Fortran (gfortran), C++ (g++)
+    Linux 3.10.0-327.10.1.el7     GNU C (gcc), Fortran (gfortran), C++ (g++)
     #1 SMP x86_64 GNU/Linux       compilers:
-    (kituo/moohan)                  Version 4.8.3 20140911 (Red Hat 4.8.3-9)
-                                    Version 5.2.0
+    (kituo/moohan)                  Version 4.8.5 20150623 (Red Hat 4.8.5-4)
+                                    Versions 4.9.3, 5.2.0
                                   Intel(R) C (icc), C++ (icpc), Fortran (icc)
                                   compilers:
                                      Version 15.0.3.187 Build 20150407
@@ -236,24 +254,26 @@ They are built with the configure process unless specified otherwise.
                                   Visual Studio 2013 w/ Intel Fortran 15 (cmake)
                                   Visual Studio 2015 w/ Intel Fortran 16  (cmake)
 
-    Windows 8.1                   Visual Studio 2012 w/ Intel Fortran 15 (cmake)
-                                  Visual Studio 2013 w/ Intel Fortran 15 (cmake)
+    Windows 10                    Visual Studio 2015 w/ Intel Fortran 16 (cmake)
 
-    Windows 8.1 x64               Visual Studio 2012 w/ Intel Fortran 15 (cmake)
-                                  Visual Studio 2013 w/ Intel Fortran 15 (cmake)
+    Windows 10 x64                Visual Studio 2015 w/ Intel Fortran 16 (cmake)
 
-    Mac OS X Mt. Lion 10.8.5      Apple clang/clang++ version 5.1 from Xcode 5.1
+    Mac OS X Mt. Lion 10.8.5      Apple LLVM version 5.1 (clang-503.0.40)
     64-bit                        gfortran GNU Fortran (GCC) 4.8.2
     (swallow/kite)                Intel icc/icpc/ifort version 15.0.3
 
-    Mac OS X Mavericks 10.9.5     Apple clang/clang++ version 6.0 from Xcode 6.2.0
+    Mac OS X Mavericks 10.9.5     Apple LLVM version 6.0 (clang-600.0.57)
     64-bit                        gfortran GNU Fortran (GCC) 4.9.2
     (wren/quail)                  Intel icc/icpc/ifort version 15.0.3
 
-    Mac OS X Yosemite 10.10.5     Apple clang/clang++ version 6.0 from Xcode 7.0.0
+    Mac OS X Yosemite 10.10.5     Apple LLVM version 6.1 (clang-602.0.53)
     64-bit                        gfortran GNU Fortran (GCC) 4.9.2
     (osx1010dev/osx1010test)      Intel icc/icpc/ifort version 15.0.3
 
+    Mac OS X El Capitan 10.11.4   Apple LLVM version 7.3.0 clang-703.0.29)
+    64-bit                        gfortran GNU Fortran (GCC) 5.2.0
+    (VM osx1011dev/osx1011test)   Intel icc/icpc/ifort version 16.0.2
+
 
 Tested Configuration Features Summary
 =====================================
@@ -275,11 +295,11 @@ SunOS 5.11 64-bit                       n        y/y    n        y    y     y
 Windows 7                               y        y/y    n        y    y     y
 Windows 7 x64                           y        y/y    n        y    y     y
 Windows 7 Cygwin                        n        y/y    n        y    y     n
-Windows 8.1                             n        y/y    n        y    y     y
-Windows 8.1 x64                         n        y/y    n        y    y     y
+Windows 10                              n        y/y    n        y    y     y
+Windows 10 x64                          n        y/y    n        y    y     y
 Mac OS X Mountain Lion 10.8.5 64-bit    n        y/y    n        y    y     y
 Mac OS X Mavericks 10.9.5 64-bit        n        y/y    n        y    y     y
-Mac OS X Yosemeti 10.10.5 64-bit        n        y/y    n        y    y     y
+Mac OS X Yosemite 10.10.5 64-bit        n        y/y    n        y    y     y
 AIX 6.1 32- and 64-bit                  n        y/n    n        y    y     y
 CentOS 6.7 Linux 2.6.32 x86_64 GNU      y        y/y    y        y    y     y
 CentOS 6.7 Linux 2.6.32 x86_64 Intel    n        y/y    n        y    y     y
@@ -295,11 +315,11 @@ SunOS 5.11 64-bit                          y       y         y         y
 Windows 7                                  y       y         y         y
 Windows 7 x64                              y       y         y         y
 Windows 7 Cygwin                           n       n         n         y
-Windows 8.1                                y       y         y         y
-Windows 8.1 x64                            y       y         y         y
+Windows 10                                 y       y         y         y
+Windows 10 x64                             y       y         y         y
 Mac OS X Mountain Lion 10.8.5 64-bit       y       n         y         y
 Mac OS X Mavericks 10.9.5 64-bit           y       n         y         y
-Mac OS X Yosemeti 10.10.5 64-bit           y       n         y         y
+Mac OS X Yosemite 10.10.5 64-bit           y       n         y         y
 AIX 6.1 32- and 64-bit                     y       n         n         y
 CentOS 6.7 Linux 2.6.32 x86_64 GNU         y       y         y         y
 CentOS 6.7 Linux 2.6.32 x86_64 Intel       y       y         y         y
@@ -316,50 +336,45 @@ More Tested Platforms
 =====================
 The following platforms are not supported but have been tested for this release.
 
-    Linux 2.6.18-431.11.2.el6     g95 (GCC 4.0.3 (g95 0.94!)
+    Linux 2.6.32-573.22.1.el6     g95 (GCC 4.0.3 (g95 0.94!)
     #1 SMP x86_64 GNU/Linux
     (platypus)
 
-    Mac OS X El Capitan 10.11     Apple clang/clang++ version 7.0.0 from Xcode 7.0.1
-    64-bit                        gfortran GNU Fortran (GCC) 5.2.0
-    (VM)
-
-    Windows 7                     Visual Studio 2008  (cmake)
-
-    Windows 7 x64                 Visual Studio 2008  (cmake)
-
-    Windows 10                    Visual Studio 2013 w/ Intel Fortran 15 (cmake)
-
-    Windows 10 x64                Visual Studio 2013 w/ Intel Fortran 15 (cmake)
-
-    Debian7.5.0 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
-                                  gcc (Debian 4.7.2-5) 4.7.2
-                                  GNU Fortran (Debian 4.7.2-5) 4.7.2
+    Debian8.4.0 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1 x86_64 GNU/Linux
+                                  gcc (Debian 4.9.2-10) 4.9.2
+                                  GNU Fortran (Debian 4.9.2-10) 4.9.2
                                   (cmake and autotools)
 
-    Fedora20 3.15.3-200.fc20.x86_64 #1 SMP x86_64 x86_64 x86_64 GNU/Linux
-                                  gcc (GCC) 4.8.3 20140624 (Red Hat 4.8.3-1)
-                                  GNU Fortran (GCC) 4.8.3 20140624 (Red Hat 4.8.3-1)
+    Fedora24 4.7.2-201.fc24.x86_64 #1 SMP x86_64 x86_64 x86_64 GNU/Linux
+                                  gcc (GCC) 6.1.1 20160621 (Red Hat 6.1.1-3)
+                                  GNU Fortran (GCC) 6.1.1 20160621 (Red Hat 6.1.1-3)
                                   (cmake and autotools)
 
-    SUSE 13.1 3.11.10-17-desktop #1 SMP PREEMPT x86_64 x86_64 x86_64 GNU/Linux
-                                  gcc (SUSE Linux) 4.8.1
-                                  GNU Fortran (SUSE Linux) 4.8.1
+    CentOS 7.2 3.10.0-327.28.2.el7.x86_64 #1 SMP x86_64 x86_64 x86_64 GNU/Linux
+                                  gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
+                                  GNU Fortran (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
                                   (cmake and autotools)
 
-    Ubuntu 14.04 3.13.0-35-generic #62-Ubuntu SMP x86_64 GNU/Linux
-                                  gcc (Ubuntu/Linaro 4.9.1-0ubuntu1) 4.9.1
-                                  GNU Fortran (Ubuntu/Linaro 4.9.1-0ubuntu1) 4.9.1
+    Ubuntu 16.04 4.4.0-38-generic #62-Ubuntu SMP x86_64 GNU/Linux
+                                  gcc (Ubuntu 5.4.0-6ubuntu1~16.04.2) 5.4.0
+                                  GNU Fortran (Ubuntu 5.4.0-6ubuntu1~16.04.2) 5.4.0
                                   (cmake and autotools)
 
-    hopper.nersc.gov              PrgEnv-gnu/5.2.40
-                                  gcc (GCC) 4.9.2 20141030 (Cray Inc.)
-                                  GNU Fortran (GCC) 4.9.2 20141030 (Cray Inc.)
-                                  g++ (GCC) 4.9.2 20141030 (Cray Inc.)
-
 
 Known Problems
 ==============
+* Currently, the Packet Table doesn't provide a way to specify memory datatype
+  when the packet table is read.  To work around this limitation, an
+  application can use the following approach:
+  + For the C API of the Packet Table
+    - call the PT API H5PTget_type to get the datatype of the packet table
+    - call the C API H5Tget_native_type to get the native type of that datatype
+  + For the C++ API of the Packet Table
+    - call the member function PacketTable::GetDatatype to get the datatype
+      of the packet table
+    - call the C API H5Tget_native_type to get the native type of that datatype
+  (BMR, 2016/10/27, HDFFV-9758)
+
 * On windows platforms in debug configurations, the VFD flush1 tests will fail
   with the split and multi VFD drivers. These tests will display a modal debug
   dialog which must be answered or wait for the test timeout to expire.