mirror of
https://github.com/HDFGroup/hdf5.git
synced 2025-02-11 16:01:00 +08:00
---------------------- ./Makefile.in ./configure.in ./configure [REGENERATED] ./src/H5config.h.in [REGENERATED] ./config/commence.in ./config/conclude.in ./config/dec-osf4.x ./config/depend.in ./config/freebsd ./config/linux-gnu ./config/linux-gnulibc1 ./config/linux-gnulibc2 ./config/solaris2.x ./examples/Makefile.in ./src/Makefile.in ./test/Makefile.in ./testpar/Makefile.in ./tools/Makefile.in ./tools/testh5dump.sh Changes that allow hdf5 to be configured and compiled in a directory other than the source directory. This is especially useful if you want to concurrently compile with different compilers and/or compile flags, or if the hdf5 source is on read-only media like a CDROM. The changes were surprisingly easy ;-) Here's what you can do now... $ mkdir /tmp/build1 # or something $ cd /tmp/build1 $ /cdrom/hdf5/configure # where ever the source is $ make Paul, you'll have to change the testh5toh4 script similar to the way I changed testh5dump.sh. I started working on it but then gave up because of a number of problems: (1) I had to comment out all the tests that let h5toh4 choose the output file name because it always tried to put the output file in the same directory as the input file, (2) if path names are used during the h4 dump then they interfere with the diff. The test works fine when run in the source directory, but try this instead: $ gunzip <hdf5-1.1.67.tar.gz |tar xf - $ chmod -R ugo-w hdf5-1.1.67 $ mkdir build $ cd build $ ../hdf5-1.1.67/configure $ make check Dan, I didn't modify the pablo/Makefile.in because I have no way to test it. I think all you need to do is add a couple lines before the @COMMENCE@ line and add a couple search directories for header files. Anyway, it seems like almost an exact duplicate of the src/Makefile.in, so it shouldn't be a problem... ./Makefile.in Removes a few more temporary files during make clean and distclean. ./configure.in I fixed the creation of the time-stamp files so that the initial make doesn't have to regenerated all the makefiles (only GNU make users will see any change). ./src/H5R.c Changed a return type from `intn' to `int' for an API function. ./src/H5detect.c Added the volatile qualifier to a couple more variables. ./tools/h5tools.c Fixed a compiler warning about an unused local. ./tools/h5toh4.c Initialized `optind' to 1 because it's zero on my system. It should always be one on a unix system. ./tools/testh5toh4 Redirected "broken pipe" messages to /dev/null so outut is formatted correctly. |
||
---|---|---|
.. | ||
Makefile.ascired | ||
Makefile.ibmsp | ||
Makefile.in | ||
Makefile.irix64 | ||
README | ||
t_dset.c | ||
t_file.c | ||
t_mpi.c | ||
testphdf5.c | ||
testphdf5.h |
hdf5/testpar/README ------------------- (last update: Aug the 1998) This directory holds tests for the parallel HDF5 library. It is in its "infancy" and is not integrated with the rest of the HDF5 software yet. It will be smothed out in the next release. Steps to compile and test: 1a) Makefile.irix64 is one that works for IRIX64 -64 platform. You may use it as a template to create Makefile for other platforms. 1b) Makefile.ascired is one that works for the ASCI Red platform. 2) "make all -f Makefile.xxxxx >&! make.out1" creates testphdf5. 3) "make test -f Makefile.xxxxx >&! make.out2" runs testphdf5. When running "make test -f Makefile.xxxxx" the line that executes is: $(RUN) testphdf5 $(TEST_FLAGS) For the ASCI Red users: In the file Makefile.ascired, the variables RUN and TEST_FLAGS are: RUN=yod -sz 8 TEST_FLAGS=-f "pfs:/pfs/multi/tmp_1/your_own" The TEST_FLAGS variable contains an optional file prefix which needs to be changed to your own Intel PFS directory name. /* change "your_own" to your own directory name */ RUN=yod -sz 8 TEST_FLAGS=-f "pfs:/pfs/multi/tmp_1/my_dir" After the above change to Makefile.ascired, upon execution of "make test -f Makefile.ascired >&! make.out2", the prefix will be attached to filenames in testphdf5 at execution. ---- Questions? Send mail to hdfparallel@ncsa.uiuc.edu