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:
