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
23 lines
690 B
Plaintext
23 lines
690 B
Plaintext
#############################
|
|
output for 'h5ls -v tvldtypes1.h5'
|
|
#############################
|
|
Opened "tvldtypes1.h5" with sec2 driver.
|
|
Dataset1.0 Dataset {4/4}
|
|
Location: 1:976
|
|
Links: 1
|
|
Storage: information not available
|
|
Type: variable length of
|
|
native int
|
|
Dataset2.0 Dataset {4/4}
|
|
Location: 1:1576
|
|
Links: 1
|
|
Storage: information not available
|
|
Type: variable length of
|
|
native float
|
|
Dataset3.0 Dataset {SCALAR}
|
|
Location: 1:6272
|
|
Links: 1
|
|
Storage: information not available
|
|
Type: variable length of
|
|
native int
|