summaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorRobb Matzke <matzke@llnl.gov>1999-03-03 23:17:48 (GMT)
committerRobb Matzke <matzke@llnl.gov>1999-03-03 23:17:48 (GMT)
commitea3624e133ef35ec9c2c3f816a3afdbfb6b83156 (patch)
tree8d13c1c600a8ab25da627a64aa61818f00695098 /tools
parent2925631a496cbd9890e967946b46c974998b13cd (diff)
downloadhdf5-ea3624e133ef35ec9c2c3f816a3afdbfb6b83156.zip
hdf5-ea3624e133ef35ec9c2c3f816a3afdbfb6b83156.tar.gz
hdf5-ea3624e133ef35ec9c2c3f816a3afdbfb6b83156.tar.bz2
[svn-r1115] Changes since 19990302
---------------------- ./INSTALL ./configure.in ./configure [REGENERATED] ./src/H5config.h.in [REGENERATED] Improvements for parallel library. If you have a properly working mpicc you should be able to just say: $ CC=mpicc ./configure and you will see checking for mpirun... /usr/local/mpi/bin/mpirun checking for parallel support files... skipped checking how to run on one processor... /usr/local/mpi/bin/mpirun -np 1 checking how to run in parallel... /usr/local/mpi/bin/mpirun -np $$NPROCS To quote from the INSTALL file.... *** Parallel vs. serial library The HDF5 library can be configured to use MPI and MPI-IO for parallelizm on a distributed multi-processor system. The easy way to do this is to have a properly installed parallel compiler (e.g., MPICH's mpicc or IBM's mpcc) and supply that executable as the value of the CC environment variable: [NOTE: mpcc is not tested yet] $ CC=mpcc ./configure $ CC=/usr/local/mpi/bin/mpicc ./configure If no such wrapper script is available then you must specify your normal C compiler along with the distribution of MPI/MPI-IO which is to be used (values other than `mpich' will be added at a later date): $ ./configure --enable-parallel=mpich If the MPI/MPI-IO include files and/or libraries cannot be found by the compiler then their directories must be given as arguments to CPPFLAGS and/or LDFLAGS: $ CPPFLAGS=-I/usr/local/mpi/include \ LDFLAGS=-L/usr/local/mpi/lib/LINUX/ch_p4 \ ./configure --enable-parallel=mpich If a parallel library is being built then configure attempts to determine how to run a parallel application on one processor and on many processors. If the compiler is mpicc and the user hasn't specified values for RUNSERIAL and RUNPARALLEL then configure chooses `mpirun' from the same directory as `mpicc': RUNSERIAL: /usr/local/mpi/bin/mpirun -np 1 RUNPARALLEL: /usr/local/mpi/bin/mpirun -np $${NPROCS:=2} The `$${NPROCS:=2}' will be substituted with the value of the NPROCS environment variable at the time `make check' is run (or the value 2). ./testpar/Makefile.in Saying `make check' (or `make test') will run the tests on two processors by default. If you define NPROCS then that many processors are used instead: $ NPROCS=4 make check ./configure.in Fixed (hopefully) bugs with detecting whether __attribute__ and __FUNCTION__ are special keywords for the compiler. ./Makefile.in Saying `make install' from the top level directory shows instructions for using shared libraries. ./config/commence.in ./src/Makefile.in ./test/Makefile.in ./testpar/Makefile.in ./tools/Makefile.in Moved the @top_srcdir@ into the makefiles because it was expanded too early and had the wrong value. ./INSTALL Added a warning that if the wrong version of hdf4 tools are installed then `make check' will fail in the tools directory.
Diffstat (limited to 'tools')
-rw-r--r--tools/Makefile.in1
1 files changed, 1 insertions, 0 deletions
diff --git a/tools/Makefile.in b/tools/Makefile.in
index 1c75c00..723d930 100644
--- a/tools/Makefile.in
+++ b/tools/Makefile.in
@@ -5,6 +5,7 @@
#
#
@COMMENCE@
+top_srcdir=@top_srcdir@
# Add include directory to the C preprocessor flags, add -lh5tools and
# -lhdf5 to the list of libraries.