summaryrefslogtreecommitdiffstats
path: root/release_docs/INSTALL_parallel
diff options
context:
space:
mode:
authorAlbert Cheng <acheng@hdfgroup.org>2009-11-04 21:48:08 (GMT)
committerAlbert Cheng <acheng@hdfgroup.org>2009-11-04 21:48:08 (GMT)
commit6d639e66b731d832236dbb133eb3ec4746b39afd (patch)
treed78d116be26dd8c26c8431638771caf570f25b2b /release_docs/INSTALL_parallel
parent28ae489de3af1cecf1aacca89a8b7824eebbc06b (diff)
downloadhdf5-6d639e66b731d832236dbb133eb3ec4746b39afd.zip
hdf5-6d639e66b731d832236dbb133eb3ec4746b39afd.tar.gz
hdf5-6d639e66b731d832236dbb133eb3ec4746b39afd.tar.bz2
[svn-r17829] Updated the part of IBM SP to make it clearer why single process is needed
during the build part.
Diffstat (limited to 'release_docs/INSTALL_parallel')
-rw-r--r--release_docs/INSTALL_parallel16
1 files changed, 10 insertions, 6 deletions
diff --git a/release_docs/INSTALL_parallel b/release_docs/INSTALL_parallel
index a4c0d33..2a99a74 100644
--- a/release_docs/INSTALL_parallel
+++ b/release_docs/INSTALL_parallel
@@ -51,17 +51,21 @@ parallel HDF5 with one of the above, just set CC as it and configure.
The "--enable-parallel" is optional in this case.
$ CC=/usr/local/mpi/bin/mpicc ./configure --prefix=<install-directory>
- $ make
- $ make check
+ $ make # build the library
+ $ make check # verify the correctness
+ # Read the Details section about parallel tests.
$ make install
2.2. IBM SP
-----------
-Make sure your environment variables are set correctly to compile and execute
-a single process mpi applications for the SP machine. Unfortunately, the
-setting varies from machine to machine. E.g., the following works for the
-IBM SP machine at LLNL.
+During the build stage, the H5detect is compiled and executed to generate
+the source file H5Tinit.c which is compiled as part of the HDF5 library. In
+parallel mode, make sure your environment variables are set correctly to
+execute a single process mpi application. Otherwise, multiple processes
+attempt to write to the same H5Tinit.c file, resulting in a scrambled
+source file. Unfortunately, the setting varies from machine to machine.
+E.g., the following works for the IBM SP machine at LLNL.
setenv MP_PROCS 1
setenv MP_NODES 1