2 # This is one of a set of test that generate checksums after files are
3 # created. Generally a bitmap if first produced by a program such as sym_strip,
4 # rect_in_rect, rect_cen_in_rect, circ_in_circ, circ_in_rect,
5 # generate_coupler_bitmap etc.
7 # In a few cases, the checksum is performed on a file that is
8 # supplied with the package, rather than one that is
11 # The checksum of the bitmaps generated is compared to what is known to be
12 # the correct checksum using a program 'mymd5sum' which is a cut-down version of
13 # the normal md5 or md5sum command. It does not print the filename
14 # to stdout, as the normal version does.
16 # Due to rounding errors, some systems do generate a different checksum on
17 # one machines to another. Usually this is only a single pixel differing
18 # by one gray level. In this case, the 3 consequive bytes 301041,
19 # 301042 and 301043 are 254 on a Cray Y-MP but 255 on a Sun. AS such,
20 # in this case, more than one checksum is acceptable.
22 touch $top_builddir/tmp/test_sym_strip.U.bmp
24 MD5SUM=`$top_builddir/tools/src/mymd5sum $top_builddir/tmp/test_sym_strip.U.bmp`
25 if [ $MD5SUM = 2f4d1ab071f103805e794a9b1cdba7ce ] ; then
26 rm -f $top_builddir/tmp/test_sym_strip.U.bmp
27 echo "PASSED:" $0 >> tests.log
30 echo "FAILED:" $0 >> tests.log