| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Description: Typo in the configure.in script. CC_VERSION should be set using
CC_NOFLAGS, but is currently using CC_NOFLAG, which does not exist.
Tested: kagiso (configure issue)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description: Tests in perform directory were never getting run, and
h5perf* programs were not being installed.
Solution: Added another build option, 'make check-perform', which runs the
tests in the perform directory. Also modified the Makefiles in the
perform directory to install (with 'make install') h5perf when
parallel is enabled, and h5perf and h5perf_serial when parallel
is disabled.
Tested: kagiso, smirom, linew
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description: Applying update to autotools that was applied to 1.8 a couple
of weeks ago to the trunk.
Updated bin/reconfigure script to reflect the new versions of
libtool and automake in the /home1/packages/ directory.
Rearranged configure.in script. When using libtool 2.2.2, the
libtool script doesn't generate until later in the configuration
process, so I had to move a test that parsed through the libtool
script to a point after where it was actually being generated.
Ran libtoolize on the project, and ran bin/reconfigure to
regenerate configure and Makefile.in's throughout.
Tested: kagiso, smirom, linew (h5committest)
|
| |
|
|
|
|
| |
New fortran wrappers added.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The development branch was changed to default enable-production for the
v1.8 release but had not switched back to default development mode.
Solution:
Changed it back to --disable-production (aka development) as the default.
Also ran bin/reconfigure to update configure.
Tested:
Smirom only. No h5committest since the change is trivial and if it works
at smirom, it should work everywhere else.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Description:
Previously, we created a patch for Cygwin to skip checking for the timezone variable. We made this change in both the trunk and hdf5_1_8 branch. However, in the branch version, we seemed to have used wrong quotes in our check ('uname' rather than `uname`). This corrects the typo
Tested:
Cygwin on WinXP
|
|
|
|
|
|
|
|
| |
Description:
This is the same patch that Mike McGreevy helped me with on the 1.8 branch. The latest cygwin DLL has trouble with the global timezone variable. Now in configure, we target CYGWIN with a case statement, and avoid the problem.
Tested:
Cygwin on WinXP
|
|
|
|
|
|
| |
the HDF5 developers meeting
on February 8, 2008; modified docs files to point to the documentation snapshots.
|
| |
|
|
|
|
|
|
| |
the release.
|
|
|
|
|
|
|
|
|
|
|
| |
Description: config/lt_vers.am was updated as follows due to changes in API
since last version update:
LT_VERS_INTERFACE = 5
LT_VERS_REVISION = 0
LT_VERS_AGE = 0
Tested: kagiso
|
|
|
|
| |
Changed version number to hdf501.8.0-rc3 using bin/h5vers script
|
|
|
|
|
|
|
|
| |
server and changed
the version to hdf5-1.8.0-rc2 using bin/h5vers script.
Platforms tested: ran test for hdf5-1.8.0-rc1 source on kagiso after craeting public tar ball.
|
|
|
|
|
|
| |
Tested: kagiso only. Not need for h5committest since it is a configure simple
change. If it works correct in kagiso, it should work the same for all other
machines.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add work-around to allow reading files that were produced with a buggy
earlier version of the library, which could create objects with the wrong
object header message count. There is now a configure flag
"--enable-strict-format-checks" which triggers a failure on reading a file
with this sort of corruption (when enabled) and allows the object to be read
(when disabled). The default value for the "strict-format-checks" flag is
yes when the "debug" flag is enabled and no when the "debug" flag is disabled.
Note that if strict format checks are disabled (allowing objects with
this particular kind of corruption to be read) and the file is opened with
write access, the library will re-write the object header for the corrupt
object with the correct # of object header messages.
This closes bugzilla bug #1010.
Tested on:
FreeBSD/32 6.2 (duty) in debug mode
FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode
Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe,
in debug mode
Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Mac OS X/32 10.4.10 (amazon) in debug mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
|
|
|
|
|
|
|
|
| |
filters
usage is to repeat the -f option
tested: windows, linux, solaris
|
|
|
|
|
|
|
|
| |
1.8.0-rc1 (stands for
1.8.0 release candidate # 1)
Platforms tested: none, minor change with the known script.
|
|
|
|
|
|
|
|
| |
1.8.0-beta5 by running
bin/h5vers script
Platforms tested: kagiso (minor change)
|
|
|
|
|
|
|
|
|
|
| |
Removed the stream-vfd from the basic library code.
(The stream-vfd source files are not removed yet but the MANIFEST has been
updated to NOT release those stream-vfd source files.)
Platforms tested:
Kagiso and smirom.
Then test the release tar ball in kagiso.
|
|
|
|
|
|
|
|
|
|
| |
link was opened twice, the library
had some trouble to close in the end. The problem came from the field "holding_file" of
H5O_loc_t. It's used to indicate special links like external links. The fix is to turn it off
whenever H5O_open is called. Later the caller function should turn it on when it needs to.
Tested on kagiso, linew, and smirom.
|
|
|
|
| |
1.8.0-beta4post1
|
|
|
|
|
|
| |
1.8.0-beta4
Platforms tested: kagiso only (trivial change using bin/h5vers script)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove --enable-hdfv1_6 configure flag, now that all dependencies on it
have been removed and new --with-default-api-version=[v16|v18] and
--disable-deprecated-symbols flags have taken its place.
Update types in bin/trace so that bin/reconfigure runs cleanly.
Run bin/reconfigure to regenerate configure script, along with
other associated files, etc.
Tested on:
FreeBSD/32 6.2 (duty) in debug mode
FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode
Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe,
in debug mode
Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Mac OS X/32 10.4.10 (amazon) in debug mode
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
First real use of API versioning code, H5E routines switched to use
new API versioning scheme.
Tested on:
Mac OS X/32 10.4.10 (amazon)
FreeBSD/32 6.2 (duty)
FreeBSD/64 6.2 (liberty)
Linux/32 2.6 (kagiso)
Linux/64 2.6 (smirom)
Solaris/32 5.10 (linew)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. In H5Dwrite and H5Dread, let the data buffer point to a fake address if the application passes
in an empty buffer. This is mainly for MPIO programs that some processes may not have any
data to write or read but still participate the I/O. This solution solves some MPI's problem
like the ChaMPIon on tungsten which doesn't support empty buffer.
2. The ChaMPIon on tungsten doesn't support complex derived MPI data type correctly and collective
I/O when some processes don't have any data to write or read correctly. Detect the compiler
"cmpicc" in the system-specific config file and set the variables for these two cases to false.
The PHDF5 library already has set up a way to switch collective chunked I/O to independent
under these two cases.
3. A bug fix - During the work of the optimization for compound data I/O, the case for switching
collective chunked I/O to independent I/O was leftout. Fixed it by adding I/O caching to it in
H5D_multi_chunk_collective_io in H5Dmpio.c.
Tested on tungsten, cobalt, and kagiso for parallel; on linew and smirom for serial.
|
|
|
|
|
|
|
| |
Description: This flag causes problems for users and is difficult to
support in the library. It has been removed. (see Bug 708).
Tested: kagiso, linew
|
|
|
|
|
|
|
| |
Description: Configure will now detect the presence of the 'siglongjmp' function. If present,
the macro H5_HAVE_SIGLONGJMP will be defined in src/H5pubconf.h.
Tested: kagiso, smirom, linew
|
|
|
|
| |
bin/h5vers script
|
|
|
|
|
|
|
| |
into INSTALL file for the 1.8.0-beta* releases
Tested: Release tar ball is available on the frp server, It was tested on kagiso with the PGI compilers.
|
|
|
|
|
|
|
|
|
|
| |
reorganization.
Description:
move the h5stat tool into its own directory.
Platform tested:
kagiso.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove stray reference to "group revision" configure flag
Remove Windows-specific EOL characters from src/H5FDwindows.c
Add some missing types to bin/trace
Re-run bin/reconfigure script to regenerate information after changes above.
Tested on:
FreeBSD/32 6.2 (duty)
FreeBSD/64 6.2 (liberty)
Linux/32 2.6 (linux)
Solaris/32 2.10 (linew)
|
|
|
|
|
|
|
|
|
|
| |
Re-ran bin/reconfigure
Tested on:
FreeBSD/32 6.2 (duty)
FreeBSD/64 6.2 (liberty)
Linux/32 2.6 (kagiso)
Solaris/32 2.10 (linew)
|
|
|
|
|
|
|
|
|
| |
Add --with-default-api-version configure flag.
Tested on:
Mac OS X/32 10.4.10 (amazon)
FreeBSD/32 6.2 (duty)
Linux/32 2.6 (kagiso)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add --enable-deprecated-symbols configure option, to allow users to
remove deprecated public API symbols at configure time.
Add bin/make_vers script to bin/reconfigure actions.
Run bin/reconfigure to regenerate autotool components.
Tested on:
Mac OS X/32 10.4.10 (amazon)
FreeBSD/32 6.2 (duty)
Linux/32 2.6 (kagiso)
|
|
|
|
|
|
|
|
|
|
| |
src/H5pubconf.h file.
2) Removing configuration of c++/src/H5cxx_pubconf.h file.
Reasoning: the additional pubconf file caused compilation complications, this is cleaner.
Tested: kagiso, smirom
|
|
|
|
|
|
|
|
|
|
| |
Description: added new configuration to generate a pubconf file
in the c++/src directory, H5cxx_pubconf.h. When C++
compiler recognizes 'offsetof', the macro
H5_CXX_HAVE_OFFSETOF is defined in the new
pubconf file.
tested: kagiso, smirom
|
|
|
|
| |
change version number to 1.8.0-beta2poat1
|
|
|
|
| |
Changed version number to 1.8.0-beta2
|
|
|
|
| |
ball for remote testing
|
|
|
|
|
|
|
| |
preparation for remote testing
for the HDF5 1.8.0-beta2 release
Platforms tested: kagiso (small change done by bin/h5vers script)
|
|
|
|
|
|
|
|
| |
Description: When the compiler has the __offsetof__ extension, the
H5_HAVE_OFFSETOF macro will be defined. When the compiler
does not have the extension, the macro will remain undefined.
Tested: kagiso
|
|
|
|
|
|
|
|
|
|
|
| |
Hook "default VFD" configure macros into library.
Also, make "default VFD" default to sec2 instead of nothing.
Tested on:
FreeBSD/32 6.2 (duty)
FreeBSD/64 6.2 (liberty)
Mac OS X/32 10.4.9 (amazon)
|
|
|
|
|
|
|
|
| |
Description: this flag will define the macro H5_DEFAULT_VFD in src/pubconf.h
and set it to be either H5FD_SEC2 or H5FD_STDIO, depending on the
value set with the configuration flag (either sec2 or stdio).
Tested: kagiso, smirom, linew
|