summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--release_docs/INSTALL_TFLOPS56
1 files changed, 30 insertions, 26 deletions
diff --git a/release_docs/INSTALL_TFLOPS b/release_docs/INSTALL_TFLOPS
index b3e8421..cf8ab1e 100644
--- a/release_docs/INSTALL_TFLOPS
+++ b/release_docs/INSTALL_TFLOPS
@@ -1,36 +1,32 @@
-
FOR THE INTEL TFLOPS MACHINE:
Below are the step-by-step procedures for building, testing, and
-installing both the sequential and parallel versions of the HDF5 library.
+installing the parallel and sequential versions of the HDF5 library.
-----------------
Software locations
------------------
The zlib compression library is installed in /usr/community/hdf5/ZLIB.
-The mpich library, including mpi-io support, is in
-/usr/community/mpich/mpich-1.2.1.
+The latest version is zlib v1.1.3.
+The mpich library, including mpi-io support, is in /usr/community/mpich/.
+The latest version used is mpich-1.2.3.
---------------
-Sequential HDF5:
+Parallel HDF5:
---------------
-The setup process for building the sequential HDF5 library for the
-ASCI Red machine is done by a coordination of events from sasn100 and
-janus. Though janus can do compiling, it is better to build it
-from sasn100 which has more complete building tools and runs faster.
-It is also anti-social to tie up janus with compiling. The HDF5 building
-requires the use of janus because one of steps is to execute a program
-to find out the run-time characteristics of the TFLOPS machine.
+The setup process for building the parallel version of the HDF5 library for the
+ASCI Red machine is very similar to the sequential version. Since TFLOPS
+does not support MPIO, we have prepared a shell-script file that configures
+with the appropriate MPI library.
Assuming you have already unpacked the HDF5 tar-file into the
directory <hdf5>, follow the steps below:
-
FROM SASN100,
1) cd <hdf5>
-2) ./configure --host=i386-intel-osf1
+2) CC=/usr/community/mpich/mpich-1.2.3/bin/mpicc ./configure --host=i386-intel-osf1
You may safely ignore the WARNING message,
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
@@ -57,6 +53,7 @@ w
q
EOF
+
3) make H5detect
@@ -73,7 +70,6 @@ FROM SASN100,
When everything is finished compiling and linking,
-you can run the tests by
FROM JANUS,
7) make check
@@ -86,29 +82,37 @@ FROM JANUS,
make clean; make # re-make all binary
-Once satisfied with the test results, you can install
-the software by
+Once satisfied with the parallel test results, as long as you
+have the correct permission,
FROM SASN100,
8) make install
---------------
-Parallel HDF5:
+Sequential HDF5:
---------------
+(**NOTE** We have stopped testing sequential HDF5 for the Tflops machine
+since it has little practical value to build sequential applications for
+the Tflops machine. The instruction below are kept more for historical
+purpose.)
-The setup process for building the parallel version of the HDF5 library for the
-ASCI Red machine is very similar to the sequential version. Since TFLOPS
-does not support MPIO, we have prepared a shell-script file that configures
-with the appropriate MPI library.
+The setup process for building the sequential HDF5 library for the
+ASCI Red machine is done by a coordination of events from sasn100 and
+janus. Though janus can do compiling, it is better to build it
+from sasn100 which has more complete building tools and runs faster.
+It is also anti-social to tie up janus with compiling. The HDF5 building
+requires the use of janus because one of steps is to execute a program
+to find out the run-time characteristics of the TFLOPS machine.
Assuming you have already unpacked the HDF5 tar-file into the
directory <hdf5>, follow the steps below:
+
FROM SASN100,
1) cd <hdf5>
-2) CC=/usr/community/mpich/mpich-1.2.1/bin/mpicc ./configure --host=i386-intel-osf1
+2) ./configure --host=i386-intel-osf1
You may safely ignore the WARNING message,
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
@@ -135,7 +139,6 @@ w
q
EOF
-
3) make H5detect
@@ -152,6 +155,7 @@ FROM SASN100,
When everything is finished compiling and linking,
+you can run the tests by
FROM JANUS,
7) make check
@@ -164,8 +168,8 @@ FROM JANUS,
make clean; make # re-make all binary
-Once satisfied with the parallel test results, as long as you
-have the correct permission,
+Once satisfied with the test results, you can install
+the software by
FROM SASN100,
8) make install