diff options
| author | Pedro Vicente Nunes <pvn@hdfgroup.org> | 2009-02-26 20:21:50 (GMT) |
|---|---|---|
| committer | Pedro Vicente Nunes <pvn@hdfgroup.org> | 2009-02-26 20:21:50 (GMT) |
| commit | f8c5384aa534a60d6e23697d30d9f56c6f0257aa (patch) | |
| tree | d4d0d6c5603813f857b3c010e2c33332342c671d /test | |
| parent | 24341c6eb4bb584583efeb4b7d1592ae7f5f0680 (diff) | |
| download | hdf5-f8c5384aa534a60d6e23697d30d9f56c6f0257aa.zip hdf5-f8c5384aa534a60d6e23697d30d9f56c6f0257aa.tar.gz hdf5-f8c5384aa534a60d6e23697d30d9f56c6f0257aa.tar.bz2 | |
[svn-r16518] have 2 expected outputs for 2 h5ls runs depending if run on a big or little endian machine. Configure.in was modified to export a variable carrying endianess information to testh5ls.sh. This script then compares the current run with 2 expected outputs, one for a big-endian machine (linew was used to generate the output), other for little endian (jam was used to generate the output)
the way h5ls prints types, it starts searching for NATIVE types first. One solution would be h5ls not to detect these native types, using for example the same print datatype function that h5dump does, that would make the output look the same on all platforms ("32-bit little-endian integer" would be printed instead). Drawback, this "native" information would not be available. Other solution is to have not one but 2 expected outputs and make the shell script detect the endianess and compare with one output or other
tested: h5committest
Diffstat (limited to 'test')
| -rw-r--r-- | test/Makefile.in | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/test/Makefile.in b/test/Makefile.in index 167ff24..29f30d0 100644 --- a/test/Makefile.in +++ b/test/Makefile.in @@ -523,6 +523,7 @@ USE_FILTER_SHUFFLE = @USE_FILTER_SHUFFLE@ USE_FILTER_SZIP = @USE_FILTER_SZIP@ USINGMEMCHECKER = @USINGMEMCHECKER@ VERSION = @VERSION@ +WORDS_BIGENDIAN = @WORDS_BIGENDIAN@ abs_builddir = @abs_builddir@ abs_srcdir = @abs_srcdir@ abs_top_builddir = @abs_top_builddir@ |