[svn-r25825] Bring revisions #25509 - #25762 from trunk to revise_chunks.

h5committested.

6 files changed, 57 insertions, 60 deletions

diff --git a/release_docs/INSTALL b/release_docs/INSTALL
index 96f4f6e..2dcb9be 100644
--- a/release_docs/INSTALL
+++ b/release_docs/INSTALL
@@ -132,27 +132,31 @@ CONTENTS
         filter will succeed but the data will not be compressed.
 
 3.2. Szip (optional)
-        The HDF5 Library includes a predefined compression filter that 
-        uses the extended-Rice lossless compression algorithm for chunked 
-        datasets. For more information about Szip compression and license 
+        The HDF5 Library includes a predefined compression filter that
+        uses the extended-Rice lossless compression algorithm for chunked
+        datasets. For more information about Szip compression and license
         terms, see http://hdfgroup.org/doc_resource/SZIP/.
 
-        Precompiled Szip binaries for each supported platform and a source 
-        tar file can be found at ftp://ftp.hdfgroup.org/lib-external/szip/.
-        
-        To configure the HDF5 Library with the Szip compression filter, use 
-        the '--with-szlib=/PATH_TO_SZIP' flag. For more information, see 
+        The Szip source code can be obtained from the HDF5 Download page
+        http://www.hdfgroup.org/HDF5/release/obtain5.html#extlibs. Building
+        instructions are available with the Szip source code.
+
+        The HDF Group does not distribute separate Szip precompiled libraries,
+        but the HDF5 binaries available from
+        http://www.hdfgroup.org/HDF5/release/obtain5.html include 
+        the Szip encoder enabled binary for the corresponding platform.
+
+        To configure the HDF5 Library with the Szip compression filter, use
+        the '--with-szlib=/PATH_TO_SZIP' flag. For more information, see
         section 4.3.7, "Specifying other libraries and headers."
 
-        Starting with release 1.6.3, Szip library binaries are distributed 
-        with the encoder enabled (a license may be required to use this binary) 
-        and with the encoder disabled (freely usable without a license). 
-        If the encoder enabled binary is used, Szip compression encoding is 
-        available for an HDF5 application; if the encoder disabled binary is 
-        used, Szip compression is not available.  Szip decoding is always 
-        available for applications (i.e., an HDF5 application can always read 
-        Szip-compressed data) if the Szip filter is present, regardless of the 
-        binary used.
+        Please notice that if HDF5 configure cannot find a valid Szip library,
+        configure will not fail; in this case, the compression filter will 
+        not be available to the applications.
+
+        To check if Szip compression was successfully configured in, 
+        check the "I/O filters (external):" line in the configure output,
+        summary section, printed to the standard output.
 
 3.3. MPI and MPI-IO
         The parallel version of the library is built upon the foundation
diff --git a/release_docs/INSTALL_CMake.txt b/release_docs/INSTALL_CMake.txt
index 31e3917..b831071 100644
--- a/release_docs/INSTALL_CMake.txt
+++ b/release_docs/INSTALL_CMake.txt
@@ -292,9 +292,8 @@ Notes: CMake and HDF5
       how CMake support can be improved on any system. Visit the 
       KitWare site for more information about CMake.
             
-   3. Build and test results can be submitted to our CDash server at:
-                 cdash.hdfgroup.uiuc.edu. 
-      Please read the HDF and CDash document at:
+   3. Build and test results can be submitted to our CDash server,
+      please read the HDF and CDash document at:
                  www.hdfgroup.org/CDash/HowToSubmit. 
             
    4. See the appendix at the bottom of this file for examples of using
@@ -404,8 +403,6 @@ These five steps are described in detail below.
                 set (HDF5_NO_PACKAGES OFF CACHE BOOL "CPACK - Disable packaging" FORCE)
                 set (HDF5_ALLOW_EXTERNAL_SUPPORT "NO" CACHE STRING "Allow External Library Building (NO SVN TGZ)" FORCE)
                 set_property (CACHE HDF5_ALLOW_EXTERNAL_SUPPORT PROPERTY STRINGS NO SVN TGZ)
-                set (ZLIB_SVN_URL "http://svn.hdfgroup.uiuc.edu/zlib/trunk" CACHE STRING "Use ZLib from HDF repository" FORCE)
-                set (SZIP_SVN_URL "http://svn.hdfgroup.uiuc.edu/szip/trunk" CACHE STRING "Use SZip from HDF repository" FORCE)
                 set (ZLIB_TGZ_NAME "ZLib.tar.gz" CACHE STRING "Use ZLib from compressed file" FORCE)
                 set (SZIP_TGZ_NAME "SZip.tar.gz" CACHE STRING "Use SZip from compressed file" FORCE)
                 set (ZLIB_PACKAGE_NAME "zlib" CACHE STRING "Name of ZLIB package" FORCE)
@@ -468,9 +465,9 @@ These five steps are described in detail below.
                -DHDF5_ALLOW_EXTERNAL_SUPPORT:STRING="SVN"
                
            The options to control the SVN URL (config/cmake/cacheinit.cmake file) are:
-               ZLIB_SVN_URL:STRING="http://svn.hdfgroup.uiuc.edu/zlib/trunk"
-               SZIP_SVN_URL:STRING="http://svn.hdfgroup.uiuc.edu/szip/trunk"
-           These should be changed to your location. Also define CMAKE_BUILD_TYPE
+               ZLIB_SVN_URL:STRING="http://${svn_url}/zlib/trunk"
+               SZIP_SVN_URL:STRING="http://${svn_url}/szip/trunk"
+           ${svn_url} should be changed to your location. Also define CMAKE_BUILD_TYPE
            to be the configuration type.
            
       3.2.2  Or the external libraries (zlib and szip) can be configured
@@ -641,7 +638,7 @@ cmake_minimum_required(VERSION 2.8.10 FATAL_ERROR)
 set(CTEST_SOURCE_NAME hdf5-1.8.13)
 # this is the location of the source with ctest parameter hdf5src
 # "ctest -S HDF518LinuxCmake.cmake,hdf5src -C Release -O hdf518static.log"
-set(CTEST_SOURCE_NAME ${CTEST_SCRIPT_ARG})
+#set(CTEST_SOURCE_NAME ${CTEST_SCRIPT_ARG})
 
 # this is the location of the build directory
 set(CTEST_BINARY_NAME ${CTEST_SOURCE_NAME}/build)
@@ -693,7 +690,7 @@ set(SITE_BUILDNAME_SUFFIX "SHARED")
 #########   Following controls source update             ##########
 #set(LOCAL_UPDATE "TRUE")
 #########   Following controls source repository         ##########
-#set(REPOSITORY_URL "http://svn.hdfgroup.uiuc.edu/hdf5/branches/hdf5_1_8")
+#set(REPOSITORY_URL "http://svn.${hdfgroup_url}/hdf5/branches/hdf5_1_8")
 #comment to use a uncompressed source folder
 set(CTEST_USE_TAR_SOURCE "hdf5-1.8.13")
 ###################################################################
diff --git a/release_docs/INSTALL_parallel b/release_docs/INSTALL_parallel
index 6f60165..e5be615 100644
--- a/release_docs/INSTALL_parallel
+++ b/release_docs/INSTALL_parallel
@@ -23,8 +23,7 @@ with your system support staff of information how to compile an MPI program,
 how to run an MPI application, and how to access the parallel file system.
 There are sample MPI-IO C and Fortran programs in the appendix section of
 "Sample programs".  You can use them to run simple tests of your MPI compilers
-and the parallel file system. Also, the t_posix_compliant test in testpar
-verifies if the file system is POSIX compliant.
+and the parallel file system.
 
 
 1.2. Further Help
@@ -322,11 +321,6 @@ non-zero code.  Failure to support file size greater than 2GB is not a fatal
 error for HDF5 because HDF5 can use other file-drivers such as families of
 files to bypass the file size limit.
 
-The t_posix_compliant tests if the file system is POSIX compliant when POSIX
-and MPI IO APIs are used.  This is for information only and it always exits
-with 0 even when non-compliance errors have occurred.  This is to prevent
-the test from aborting the remaining parallel HDF5 tests unnecessarily.
-
 The t_cache does many small sized I/O requests and may not run well in a
 slow file system such as NFS disk. If it takes a long time to run it, try
 set the environment variable $HDF5_PARAPREFIX to a file system more suitable
diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt
index e38beb5..44943ce 100644
--- a/release_docs/RELEASE.txt
+++ b/release_docs/RELEASE.txt
@@ -1,4 +1,4 @@
-HDF5 version 1.9.192-swmr0 currently under development
+HDF5 version 1.9.203-swmr0 currently under development
 
 
 INTRODUCTION
@@ -1171,9 +1171,6 @@ Supported Platforms
     #1 SMP x86_64 GNU/Linux       compilers for 64-bit applications;
     (koala)                           Version 4.1.2 20080704 (Red Hat 4.1.2-54)
                                       Version 4.8.2
-                                  PGI C, Fortran, C++ for 64-bit target on 
-                                  x86-64;
-                                      Version 13.7-0 
                                   Intel(R) C, C++, Fortran Compilers for 
                                   applications running on Intel(R) 64; 
                                       Version 14.0.2 (Build 20140120)
@@ -1189,11 +1186,12 @@ Supported Platforms
                                   compilers:
                                      Version 14.0.2 (Build 20140120)
 
-    Linux 2.6.32-431.11.2.el6.ppc64 gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-3)
-    #1 SMP ppc64 GNU/Linux        g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-3)
-    (ostrich)                     GNU Fortran (GCC) 4.4.7 20120313 (Red Hat 4.4.7-3)
-                                  IBM XL C/C++ V11.1
-                                  IBM XL Fortran V13.1
+    Linux 2.6.32-431.29.2.el6.ppc64 gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4)
+    #1 SMP ppc64 GNU/Linux        g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4)
+    (ostrich)                     GNU Fortran (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4)
+                                  IBM XL C/C++ V13.1
+                                  IBM XL Fortran V15.1
+    
     Linux 2.6.32-220.23.1.1chaos  Intel C, C++, Fortran Compilers
     ch5.x86_64 GNU/Linux              Version 12.1.5.339
     (LLNL Aztec)
@@ -1209,16 +1207,20 @@ Supported Platforms
     Windows 7                     Visual Studio 2008 w/ Intel Fortran 14 (cmake)
                                   Visual Studio 2010 w/ Intel Fortran 14 (cmake)
                                   Visual Studio 2012 w/ Intel Fortran 14 (cmake)
-                                  Cygwin(CYGWIN_NT-6.1 1.7.28(0.271/5/3) gcc(4.8.2) compiler and gfortran)
+                                  Visual Studio 2013 w/ Intel Fortran 14 (cmake)
+                                  Cygwin(CYGWIN_NT-6.1 1.7.32(0.274/5/3) gcc(4.8.3) compiler and gfortran)
                                   (cmake and autotools)
 
     Windows 7 x64                 Visual Studio 2008 w/ Intel Fortran 14 (cmake)
                                   Visual Studio 2010 w/ Intel Fortran 14 (cmake)
                                   Visual Studio 2012 w/ Intel Fortran 14 (cmake)
+                                  Visual Studio 2013 w/ Intel Fortran 14 (cmake)
                                   
     Windows 8.1                   Visual Studio 2012 w/ Intel Fortran 14 (cmake)
+                                  Visual Studio 2013 w/ Intel Fortran 14 (cmake)
 
     Windows 8.1 x64               Visual Studio 2012 w/ Intel Fortran 14 (cmake)
+                                  Visual Studio 2013 w/ Intel Fortran 14 (cmake)
 
     Mac OS X Lion 10.7.3          gcc i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 from Xcode 4.2.1
     32- and 64-bit                g++ i686-apple-darwin11-llvm-g++-4.2 (GCC) 4.2.1 from Xcode 4.2.1
@@ -1303,12 +1305,12 @@ More Tested Platforms
 =====================
 The following platforms are not supported but have been tested for this release.
 
-    Linux 2.6.18-308.13.1.el5PAE  MPICH mpich 3.1 compiled with
-    #1 SMP i686 i686 i386             gcc 4.8.2 and gfortran 4.8.2
+    Linux 2.6.18-308.13.1.el5PAE  MPICH mpich 3.1.2 compiled with
+    #1 SMP i686 i686 i386             gcc 4.9.1 and gfortran 4.9.1
     (jam)                         g95 (GCC 4.0.3 (g95 0.94!)
 
-    Linux 2.6.18-431.11.2.el6     MPICH mpich 3.1 compiled with
-    #1 SMP x86_64 GNU/Linux           gcc 4.8.2 and gfortran 4.8.2
+    Linux 2.6.18-431.11.2.el6     MPICH mpich 3.1.2 compiled with
+    #1 SMP x86_64 GNU/Linux           gcc 4.9.1 and gfortran 4.9.1
     (platypus)                    g95 (GCC 4.0.3 (g95 0.94!)   
 
     FreeBSD 8.2-STABLE i386       gcc 4.2.1 [FreeBSD] 20070719
@@ -1351,14 +1353,14 @@ The following platforms are not supported but have been tested for this release.
                                   GNU Fortran (SUSE Linux) 4.8.1
                                   (cmake and autotools)
 
-    Ubuntu 14.04 3.13.0-32-generic #57-Ubuntu SMP i686 GNU/Linux
-                                  gcc (Ubuntu/Linaro 4.8.2-19ubuntu1) 4.8.2
-                                  GNU Fortran (Ubuntu/Linaro 4.8.2-19ubuntu1) 4.8.2
+    Ubuntu 14.04 3.13.0-35-generic #62-Ubuntu SMP i686 GNU/Linux
+                                  gcc (Ubuntu/Linaro 4.9.1-0ubuntu1) 4.9.1
+                                  GNU Fortran (Ubuntu/Linaro 4.9.1-0ubuntu1) 4.9.1
                                   (cmake and autotools)
 
-    Ubuntu 14.04 3.13.0-32-generic #57-Ubuntu SMP x86_64 GNU/Linux
-                                  gcc (Ubuntu/Linaro 4.8.2-19ubuntu1) 4.8.2
-                                  GNU Fortran (Ubuntu/Linaro 4.8.2-19ubuntu1) 4.8.2
+    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
                                   (cmake and autotools)
     
     Cray Linux Environment (CLE)  PrgEnv-pgi/4.0.46
diff --git a/release_docs/USING_HDF5_CMake.txt b/release_docs/USING_HDF5_CMake.txt
index 8d09b22..6195dc3 100644
--- a/release_docs/USING_HDF5_CMake.txt
+++ b/release_docs/USING_HDF5_CMake.txt
@@ -27,7 +27,7 @@ Notes: This short instruction is written for users who want to quickly
             
          3. See the appendix at the bottom of this file for an example 
             of using a ctest script for building and testing. See 
-            CMake.txt for more information.
+            INSTALL_CMake.txt for more information.
 
 
 
@@ -69,7 +69,7 @@ Go through these steps to build HDF5 applications with CMake.
    1. Run CMake
    2. Configure the cache settings
    3. Build HDF5 Applications
-   4. Test HDF5 Applications.
+   4. Test HDF5 Applications
 
 These steps are described in more detail below.
 
@@ -254,7 +254,7 @@ set(SITE_COMPILER_NAME "compiler name")
 set(SITE_COMPILER_VERSION "compiler version")
 
 # needed for source updates, change as required
-set(REPOSITORY_URL "http://svn.hdfgroup.uiuc.edu/hdf5-examples/trunk/1_8")
+set(REPOSITORY_URL "http://svn.${hdfgroup_url}/hdf5-examples/trunk/1_8")
 
 set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DCMAKE_INSTALL_PREFIX:PATH=/usr/local/hdf5Examples-1.8")
 
diff --git a/release_docs/USING_HDF5_VS.txt b/release_docs/USING_HDF5_VS.txt
index 9bf301e..9063ea6 100644
--- a/release_docs/USING_HDF5_VS.txt
+++ b/release_docs/USING_HDF5_VS.txt
@@ -18,12 +18,12 @@ Using Visual Studio 2010 with HDF5 Libraries built with Visual Studio 2010
 
    1. Set up path for external libraries and headers
 
-      The path settings will need to be in project property sheets per project. 
+      The path settings will need to be in the project property sheets per project. 
       Go to "Project" and select "Properties", find "Configuration Properties", 
       and then "VC++ Directories".
           
       1.1 If you are building on 64-bit Windows, find the "Platform" dropdown
-              and select "x64".
+          and select "x64".
               
       1.2 Add the header path to the "Include Directories" setting.
           
@@ -42,7 +42,7 @@ Using Visual Studio 2010 with HDF5 Libraries built with Visual Studio 2010
 Using Visual Studio 2008 with HDF5 Libraries built with Visual Studio 2008
 ==========================================================================
 
-   2. Set up path for external libraries and headers
+   2. Set up the path for external libraries and headers
 
       Invoke Microsoft Visual Studio and go to "Tools" and select "Options", 
       find "Projects", and then "VC++ Directories".