diff options
| -rw-r--r-- | INSTALL_Windows (renamed from INSTALL_Windows.txt) | 0 | ||||
| -rw-r--r-- | MANIFEST | 2 | ||||
| -rw-r--r-- | RELEASE | 22 |
3 files changed, 8 insertions, 16 deletions
diff --git a/INSTALL_Windows.txt b/INSTALL_Windows index 6b55683..6b55683 100644 --- a/INSTALL_Windows.txt +++ b/INSTALL_Windows @@ -10,7 +10,7 @@ ./INSTALL_TFLOPS ./INSTALL_VFL ./INSTALL_parallel -./INSTALL_Windows.txt +./INSTALL_Windows ./HISTORY ./MANIFEST ./Makefile.dist @@ -1,13 +1,13 @@ - HDF5 Release 1.4-Beta2 + HDF5 Release 1.4-Beta3 INTRODUCTION This document describes the differences between HDF5-1.2.0 and -HDF5-1.4-Beta2, and contains information on the platforms tested and -known problems in HDF5-1.4-Beta2. For more details check the HISTORY +HDF5-1.4-Beta3, and contains information on the platforms tested and +known problems in HDF5-1.4-Beta3. For more details check the HISTORY file in the HDF5 source. The HDF5 documentation can be found on the NCSA ftp server @@ -121,7 +121,7 @@ h4toh5 Utility 5. Platforms - The h4toh5 utility requires HDF5.1.4. + The h4toh5 utility requires HDF5.1.4 and HDF4r1.4 The beta h4toh5 utility has been tested on Solaris 2.6, Solaris 2.5, Irix 6.5, HPUX 11.0, DEC Unix, FreeBSD, and Windows 2000. @@ -339,6 +339,7 @@ Bug Fixes since HDF5-1.4.0-beta2 * Fixed fairly obscure bug in hyperslab I/O which could (in rare cases) not copy all the data during a transfer. * Removed ragged array code from library. + * F90 library and module files are installed properly now on all supported platforms. Platforms Tested ================ @@ -348,9 +349,9 @@ Platforms Tested AIX 4.3.2 (IBM SP) mpcc_r 3.6.6 - Cray T3E sn6711 2.0.539b Cray Standard C Version 6.3.0.2 + Cray T3E sn6711 2.0.5.43 Cray Standard C Version 6.4.0.0 Cray Fortran Version 3.4.0.2 - FreeBSD 4.2-STABLE gcc 2.95.2 + FreeBSD 4.2 gcc 2.95.2 g++ 2.95.2 HP-UX B.10.20 HP C HP92453-01 A.10.32.30 HP-UX B.11.00 HP C HP92453-01 A.11.00.13 @@ -393,15 +394,6 @@ Known Problems * h4toh5 fails on object references on the Cray T3E. -* The installation of the DEC Fortran binaries fails. It can be - done manually by copying the *.mod files from the fortran/src - directory. - -* Fortran modules may not be installed when created. The install process - tries to check for modules, but if it fails to find the correct ones, - then they won't be installed. If this occurs, simply copy those modules - to the appropriate install directory and set the permissions for them. - * SunOS 5.6 with C WorkShop Compilers 4.2: Hyperslab selections will fail if library is compiled using optimization of any level. |