Purpose:
Support portability
Description:
I forgot that source file extension .C will not work on Windows.
Solution:
Changed all source file from *.C to *.cpp for portability.
Platforms tested:
arabica (sparc-sun-solaris 2.7)
Description:
The prototype of two C API functions, H5Tget_offset and
H5Sget_simple_extent_npoints was changed to fix bug #446,
resulting in the need for updating the two corresponding
C++ API functions.
Solution:
- Changed the return type of AtomType::getOffset from size_t
to int, and the error return value from 0 to -1.
- Changed the return type of DataSpace::getSimpleExtentNpoints
from hsize_t to hssize_t, and the error value from 0 to -1.
Platforms tested:
arabica (sparc-sun-solaris 2.7)
Purpose:
updating all.dsw(adding h4toh5dll and h5toh4dll version).
adding a automatic crude test script of h4toh5 converter on windows.
Description:
Solution:
Platforms tested:
WIn 2000
Purpose:
a bug fix for windows
Description:
ignore checking the permission of file and directory on windows
Solution:
using ifndef WIN32 endif to ignore checking this feature.
Will find how windows deal with file checking stuff later.
Platforms tested:
WIN 2000, and confirmed at eirene(Linux)
Improvement
Description:
Made the Makefiles better.
Solution:
Added standard macros concerning where things are place. Like
libraries and so forth.
Platforms tested:
Linux
Purpose:
Add a crude script for automatic testing h5toh4 converter tool
Description:
the name of the script is called h5toh4testrun and is under ....../hdf5/tools directory.
Solution:
Four parameters should be typed in correctly in order to do the auto test.
1. Debug or Release version you are testing.
2. The top directory path(including the drive name) where hdf5 tools is located.
Such as D:/h5_1.4pre2
3. The full path where hdp is located.
Such as D:/H414/bin
4. If no dll version(currently not tested yet); leave this parameter empty or type DLL.
Platforms tested:
NT 4.0(NT) and 5.0(2000).
Purpose:
turn off "checking file and directory permission right" on windows platform
Description:
Adding #ifndef WIN32 #endif block at the corresponding test-file and test-dir functions.
Solution:
See above.
Platforms tested:
Win NT 4.0,5.0; and confirm the result the same on eirene and arabica
Bug Fix
Description:
The fix we put in to ignore warning 405 was incorrect. The quotes
were confusing to configure.
Solution:
Turns out that there doesn't need to be a space between the -M
flag and the warning number.
Platforms tested:
T3E
Feature
Description:
H5Eprint used to print "thread 0" even in MPI-application.
Added code to print MPI-process rank ID (as in MPI_COMM_WORLD) to
give more information of which process is printing the messages.
Platforms tested:
IRIX64-64, both serial and parallel.
Bug Fix.
Description:
Attributes whose datatype was an object or dataset region reference weren't
dumping correctly.
Solution:
Pass along attribute ID to the code which prints the attributes, so the
reference types can be dereferenced and printed.
Platforms tested:
FreeBSD 4.2 (hawkwind) & IRIX64 6.5 (modi4)
Improvement
Description:
During configure, it tries to find the size of various basic
C data types (int, int8, fast_int8, ...) by running a small
program for each data type. But Pecific blue uses a batch queue
system to launch all jobs and the whole process takes couple
minutes. With over 20 basic types to test, that takes "forever"
for the configure to complete.
Solution:
Let the configure complete, then save all those valid values in
the config.cache file into the specific config file for Pac. Blue.
With the values cached, configure does not need to run those little
problems.
Platform Tested:
Pacific blue with mpicc.
Bug fix.
Description:
Cray T3E (and J90?) was failing on partial I/O tests. The bug was in
the optimized hyperslab routines for cases where a hyperslab filled the
temporary datatype conversion buffer and the optimized hyperslab routine
needed to start in the middle of a hyperslab.
Solution:
Corrected code to detect the situation and read in the correct amount of
elements in the hyperslab.
Platforms tested:
Cray T3E (mcurie.nersc.gov)
Purpose:
Bugfix
Description:
The gcc linker couldn't resolve any socket routine symbols
if the Stream VFD was configure.
Solution:
Add the socket library to the LIBS makefile variable not just
when compiling with the native cc compiler
but also if using GNU tools (such as on Solaris x86 systems).
Platforms tested:
SunOS 5.5 with GNU cc (hatteras),
SunOS 5.6 with native cc (thor.sistec.kp.dlr.de)
Purpose:
Bugfix
Description:
Under SunOS 5.5 the symbol FIONBIO wasn't known.
Solution:
Include <sys/filio.h> which defines this symbol under Solaris.
Also put the UNUSED qualifier in the right place in a function
argument list (gcc 2.7.2 didn't like it before the type name).
Platforms tested:
SunOS 5.5 (hatteras), SunOS 5.6 t(thor.sistec.kp.dlr.de)
Purpose:
Bugfix
Description:
Under SunOS 5.5 the symbol FIONBIO wasn't known when compiling
with the Stream VFD configured.
Solution:
This symbol is defined in the system header file <sys/filio.h>.
Here we check whether this header is available.
Platforms tested:
SunOS 5.5 (hatteras), SunOS 5.6 (thor.sistec.kp.dlr.de)
Purpose:
Bug fix on T3E.
Description:
There was a typo in the h5init_types_c name translation line that
caused compilation errors.
Solution:
Fixed the typo. This fix exposes another error and I have no clue what to
do about this one
f90 -p. -p../src -dp -o fortranlib_test fortranlib_test.o hdf5test.o tH5F.o tH5D.o tH5R.o tH5S.o tH5T.o tH5Sselect.o tH5P.o tH5A.o tH5I.o tH5G.o ../src/.libs/libhdf5_fortran.a ../../src/.libs/libhdf5.a -L/u3/epourmal/HDF4/NewHDF/lib -lmfhdf -ldf -ljpeg -lz -lnsl -lm
cld-405 cld: WARNING
The entry point `HDF5' defined in relocatable object `../src/.libs/libhdf5_fortran.a[HDF5.o:HDF5]' is used; the definition in relocatable object `./../src/HDF5.o:HDF5' is ignored.
cld-431 cld: WARNING
The resulting output file `fortranlib_test' is not executable because of previous WARNING messages.
Make: "../../libtool --mode=link f90 -p. -p../src -dp -o fortranlib_test fortranlib_test.lo hdf5test.lo tH5F.lo tH5D.lo tH5R.lo tH5S.lo tH5T.lo tH5Sselect.lo tH5P.lo tH5A.lo tH5I.lo tH5G.lo ../src/libhdf5_fortran.la ../../src/libhdf5.la": Error code 1
cmd-2436 make: Stop.
+ exit 1
Make: "set -x; for d in src test examples; do \
(cd $d && make tests) || exit 1; \
done": Error code 1
Platforms tested:
T3E
Bug Fix
Description:
We were not propagating the FFLAGS macro. I.e., we were
overwriting it after it was set in the commence.in includes.
Solution:
Include it with a ``@FFLAGS@'' where we'd normally overwrite it
so that it isn't.
Platforms tested:
T3E
Attempted Bug Fix
Description:
Some machines (Cray T3E, need you ask?) use the ``-p'' flag for
enabling double precision. This breaks our Fortran interface.
Solution:
Put this test last. However, the T3E apparently doesn't need
modules, so we may have to resort to a better "fix" than this
in the future.
Platforms tested:
T3E
YABF
Description:
Needed to add the source directory for the built HDF5 library.
Solution:
Added -I../../src to the compile flags.
Platforms tested:
Linux
Bug fix
Description:
When building in a different directory, we weren't picking up the
header files correctly. The -I flag wasn't pointing to the
correct place.
Solution:
Changed the -I flag to point to the C++ source directory.
Platforms tested:
Linux
Reversal of Patch
Description:
I thought that the solaris boxen could handle the -Wc,<flag> flag
(or, rather, that libtool would do the correct thing with their
compilers). However, this isn't the case, apparently.
Solution:
Removed the ``-Wc,-LANG:std'' flag and put it in the CPPFLAGS
macro instead. This should cause it to be passed to the compiler
only...one hopes...
Following up on added tests.
Description:
Added the code to generate the vldata and array test files added into
the h5dump test suite recently. This doesn't have any affect on the
library or tools, it's just for future reference.
Platforms tested:
FreeBSD 4.2 (hawkwind)
Bug Fix
Description:
configure on Cray T3E is looking for a differently named config file,
so at it under that name.
Platforms tested:
Cray T3E (mcurie)
Bug fix
Description:
Compiler on Cray T3E has a weird problem with operations on size_t
variables.
Solution:
Change comparison to make Cray T3E happy.
Platforms tested:
Cray T3E (mcurie)
