was not updated automatically and therefore
was always outdated. Modified h5vers script to update
the version for the VMS configuration file as we do for
the similar windows file.
Platforms tested:
kagiso with bin/h5vers
Description:
- Remove need to set LD_LIBRARY_PATH when using shared szip library.
- Libtool 2.2.6a is now used to generate libraries.
- 'make check install' dependency bug is fixed, and should no longer
break the build.
- removed hard coding of shell in config/commence.am, as this causes
problems on Solaris with the new version of libtool.
- RELEASE.txt with appropriate changes.
Tested:
- kagiso, smirom, linew (merged from 1.8, pretty quick tests)
Description: Added configure test to see if pointer alignment restrictions are enforced (as in dereferencing an unaligned pointer causes an error). Added code in H5Tvlen.c to avoid dereferencing unaligned pointers, conditionally compiled based on the configure test. Added test case in dtypes.c which would previously cause such machines to fail.
Tested: kagiso, smirom, linew (h5committest); linew64
Updated utilities test scripts to make output more legible; fixed some typos.
Added four new expected output files to avoid false negative reports
for the h5dump tests (for ones that expect to have error report in them).
Updated MANIFEST to reflect the changes.
Platforms tested:
VMS server (more testing is on the way)
modified h5import test script to cleanup the files after the test;
modified "master" building script to run tools tests.
Platforms tested: VMS server (not quite done yet)
added new source file to the librray compilation script.
Platforms tested: not yet since VMS server went down; this change doesn't affect any other platform
instead of rename to get the correct names of the C++ source
files to avoid errors when build runs second time in the same directory.
Platforms tested: VMS server
Skip one of the tests in flush2.c since it looks like VMS system
flsuhes the file anyway (like on Winodws with DLLs)
Renamed files family*.h5 that are used in backward compatibility
testing to have only one '.' in a file name, otherwise VMS system
becomes confused and test fails.
Cleaned up the only test (Fortran multi-file test) that is failing on
VMS (C counterpart passesa).
Added new script to facilitate the build process on VMS
Updated MANIFEST
PLatforms tested: VMS server, kagiso and linew (minor changes)
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
H5Zpublic.h file didn't include H5public.h; done
H5Spublic.h had ghost function H5Sset_space; deleted
New source files were added to make.com for VMS.
h5gget_comment_c had a small bug in calculating buffer length; fixed
Platforms tested: pahra and kagiso; too minor for h5committest
Platforms tested:
VMS and kagiso with gcc and newly installed Absoft compiler f95
This is a minor change that affects VMS only; h5committest is not needed.
Tested platform:
Kagiso only since it is only a comment block change. If it works in one
machine, it should work in all, I hope. Still need to check the parallel
build on copper.
VMS maintenance: updated command file with the new source files;
sohm test was failing on VMS due to upper case/lower case letters in
constant and variable names (i.e. FILENAME vs. filename); modified the test
to avoid confusion.
Platforms tested:
VMS server, kagiso
Maintenance for alpha5 release; brought command files up-to-date.
Platforms tested:
VMS server. Compilation, C++, F90 and tools tests passed;
C tests are still running.
Added files created by James for user-define links to the command files
Added new script check_h5jam.com to test h5jam/h5unjam; test script
needs more work.
Platforms tested:
VMS server and test script only.
Added test script to test h5import tool; added new source file
to the make.com file in the src directory.
Platforms tested:
Only h5import was tested on the VMS server
h5ls uses -S flag to display datatype in a machine-readable form. Since
VMS is not a case sensitive system, triple quotes around S are needed; fixed.
h5ls -w80 -v -S tattr2.h5
test still reports failure due to line 311 in the tattr2.ls file "Modified: XXXX..."
Document it for now in the command file.
the last one
h5ls -w80 -v -S tattr2.h5
h5ls prints "native" for all types instead of the complete datatype definition.
I will look into the problem next.
Description: Some "" were missing causing incorrect results in passing an argument
string.
Solution: Added missing ""
Platforms tested: VMS server.
There are still problems with the tests that have
"string" as an argument, for example:
-d "/g1/g1.1/dset1.1.2[0;2;10]" tall.h5
On VMS "g1" and "dset" are translated in upper case causing h5dump
to fail. After figuring out the correct amount of " for VMS I encountered
another problem: corresponding DDL file does not have "" around
/g1/g1.1/dset1.1.2..... and therefore VMS diff fails.
Question: Since command to h5dump is
h5dump -d "/g1/g1.1/dset1.1.2[0;2;10]" tall.h5, why the second line in the
tall-5s.ddl has
h5dump -d /g1/g1.1/dset1.1.2[0;2;10] tall.h5? If one types the command
without "", it fails on UNIX.
Misc. update:
Description: More work on the test script: added all current UNIX tests.
Solution:
Platforms tested: VMS server; many tests failed but I think it is false negative.
will investigate, but for now, let's save the code.
Misc. update:
Description: Added a command file for testing tools; it has a framework
to do exactly (almost) what UNIX tools test scripts do:
- run test tool and save output
- compare output with expected result
- figure out the difference and
- print PASSED /*FAILED* in a manner similar to the UNIX output
It needs to be populated with more tests and reused for other tools.
Solution:
Platforms tested: VMS server
Misc. update:
Description: dsets and objcopy tests were missing from the command files
Solution: Added appropriate commands to compile and run tests
Platforms tested: VMS server with native float
Misc. update:
Description: Added support for Zlib compression on VMS
Solution: Modified command files to add compilation and linking with
the ZLIB library.
Platforms tested: VMS servere with the VAX floating datatype;
will test IEEE option later
Misc. update:
Purpose: Maintenance
Description: fheap test failed on VMS due to the missing H5HFiter module
Solution: Updated make.com file to include the missing module.
Platforms tested: VMS server with IEEE option.
Misc. update:
Description: Compilation of most of the Fortran files depends on existance
of three module files. On VMS the dependency was enforced by
listing source files for compilation command in the correct order.
It looks like that this approach doesn't always work and compilation fails
sometimes.
Solution: Hardcoded compilation of the threee files in the make.com file
Platforms tested: VMS server with IEEE option
Misc. update:
Description: Some VMS command files were broken, some needed
an update to catch up with the current code distribution.
Solution: Fixed
Platforms tested: VMS server with IEEE option. Will do more testing after
checking out a fresh CVS version.
Misc. update:
Description: This command file defines all necessary compilation flags
and builds all libraries, tests and examples.
If you build in a particular directory, make sure you use
the correct compilation flags since they are not defined
in each individual command file (actually the line is still there
but commented out).
Solution:
Platforms tested: VMS server
Misc. update:
Description: Some dumper tests suppose to fail; those tests cause make file
to exit.
Solution: For now I commented those tests to let other tests
to run; output is saved in a file for examination. Next step
will be to compare with the existing output. (Actually
the next step will be to learn how to program functions in DCL to
create a test script similar to UNIX one, but at least I finally
figured out why the test script was exiting.)
Platforms tested: VMS server
Misc. update:
Description: Warning message about broken line was displayed while running make.com
Solution: Replaced blank line with $ exit line.
Platforms tested: VMS server; this change is local to VMS only
Misc. update:
Description: VMS stat structure doesn't have st_blocks filed. H5_HAVE_STAT_ST_BLOCKS
was defined in h5pubconf.h and therefore compilation of big.c
failed on VMS.
Solution: Undefined H5_HAVE_STAT_ST_BLOCKS in h5pubconf.h
Platforms tested: VMS server (change is local to VMS only)
Misc. update:
Description: Linking of cache test failed on VMS due to the missing
cache_common.* files
Solution: Added cache_common.* files to the approriate places in the make.com file.
Platforms tested: VMS server (this change is for VMS only)
Misc. update:
Description: Added H5B2stat.c, H5HFflist.c and H5HFstat.c to the VMS
command file
Solution:
Platforms tested: Raymond is going to test on the VMS server
Misc. update:
Solution: Support VAX float and double types with new byte order. There're some
details not yet included,
1. the alignment detection for VAX order in H5detect.c.
2. support for special values in library conversion functions.
3. the infinity for VAX in H5T_init_inf.
4. support for VAX types in printing hexadecimal format.
Platforms tested: h5committest and fuss.
