summaryrefslogtreecommitdiffstats
path: root/release_docs/INSTALL_parallel
diff options
context:
space:
mode:
authorAlbert Cheng <acheng@hdfgroup.org>2014-11-25 23:21:39 (GMT)
committerAlbert Cheng <acheng@hdfgroup.org>2014-11-25 23:21:39 (GMT)
commit4d34b797304f6e5fd6339adbe667f9042db90126 (patch)
tree6c8b8254855001ddb6b68beecbae3752e0f63b76 /release_docs/INSTALL_parallel
parent0a212433034304f0b691019fae2a7e91d5808045 (diff)
downloadhdf5-4d34b797304f6e5fd6339adbe667f9042db90126.zip
hdf5-4d34b797304f6e5fd6339adbe667f9042db90126.tar.gz
hdf5-4d34b797304f6e5fd6339adbe667f9042db90126.tar.bz2
[svn-r25851] INSTALL_parallel already has a known issues section for Hopper.
I moved all hopper known problems from RELEASE.txt to INSTALL_parallel so that they are all in one place.
Diffstat (limited to 'release_docs/INSTALL_parallel')
-rw-r--r--release_docs/INSTALL_parallel17
1 files changed, 17 insertions, 0 deletions
diff --git a/release_docs/INSTALL_parallel b/release_docs/INSTALL_parallel
index e5be615..28068f1 100644
--- a/release_docs/INSTALL_parallel
+++ b/release_docs/INSTALL_parallel
@@ -235,6 +235,7 @@ $ make install
2.5.2 Hopper known issues
------------------------------
+Issue 1:
Sometimes when building the library with make, you might get this problem:
LD_LIBRARY_PATH="$LD_LIBRARY_PATH`echo | \
@@ -253,6 +254,22 @@ If that happens, you are probable running with make -j <x>. In that
case, you need to cleanup everything and start again as detailed above
but use serial make (do not use -j <x>).
+Issue 2:
+* When building using the Cray compilers on Cray machines, HDF5
+ configure mistakenly thinks the compiler is an intel compiler and
+ sets the -std=c99 flag which breaks configure on Cray. To build HDF5
+ properly on a Cray machine, please consult with the instructions in
+ INSTALL_parallel for building on Hopper.
+ (MSC - 2013/04/26 - HDFFV-8429)
+
+Issue 3:
+* On hopper, the build failed when RUNSERIAL and RUNPARALLEL are set
+ to aprun -np X, because the H5lib_settings.c file was not generated
+ properly. Not setting those environment variables works, because
+ configure was able to automatically detect that it's a Cray system
+ and used the proper launch commands when necessary.
+ (MSC - 2012/04/18)
+
3. Detail explanation
---------------------