Mercurial > dropbear

view libtomcrypt/run.sh @ 1227:5dde22e8a189

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
scp: Have `fatal()' append a newline to the message Date: Wed, 4 Nov 2015 20:33:19 -0000 It would seem that it's standard practice not to include a newline in the message text, but that results in poor formatting, as a shell's command line then begins on the line of the error message itself. This commit simply instructs `fatal()' to append a newline after the message, which should be suitable behavior for all of the invocations I've come across.
author Michael Witten <mfwitten@gmail.com>
date Tue, 19 Jan 2016 00:23:19 +0800
parents 0cbe8f6dbf9e
children 6dba84798cd5
line wrap: on
line source

#!/bin/bash
bash build.sh " $1" "$2 -O2" "$3 IGNORE_SPEED=1" "$4" "$5"
if [ -a testok.txt ] && [ -f testok.txt ]; then
   echo
else
	echo
	echo "Test failed"
	exit 1
fi

rm -f testok.txt
bash build.sh " $1" "$2 -Os" " $3 IGNORE_SPEED=1 LTC_SMALL=1" "$4" "$5"
if [ -a testok.txt ] && [ -f testok.txt ]; then
   echo
else
	echo
	echo "Test failed"
	exit 1
fi

rm -f testok.txt
bash build.sh " $1" " $2" " $3 " "$4" "$5"
if [ -a testok.txt ] && [ -f testok.txt ]; then
   echo
else
	echo
	echo "Test failed"
	exit 1
fi

exit 0

# $Source: /cvs/libtom/libtomcrypt/run.sh,v $   
# $Revision: 1.15 $   
# $Date: 2005/07/23 14:18:31 $