[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

1 files changed, 14 insertions, 0 deletions

diff --git a/tools/testfiles/tdataregbe.ls b/tools/testfiles/tdataregbe.ls
new file mode 100644
index 0000000..47b6994
--- /dev/null
+++ b/tools/testfiles/tdataregbe.ls
@@ -0,0 +1,14 @@
+#############################
+ output for 'h5ls -v tdatareg.h5'
+#############################
+Opened "tdatareg.h5" with sec2 driver.
+Dataset1                 Dataset {4/4}
+    Location:  1:1284
+    Links:     1
+    Storage:   information not available
+    Type:      dataset region reference
+Dataset2                 Dataset {10/10, 10/10}
+    Location:  1:744
+    Links:     1
+    Storage:   100 logical bytes, 100 allocated bytes, 100.00% utilization
+    Type:      native unsigned char