Fix on Solaris by accounting for /bin/sh there.
authorJim Wise <jwise@draga.com>
Sun, 13 Oct 2013 21:22:19 +0000 (17:22 -0400)
committerJim Wise <jwise@draga.com>
Sun, 13 Oct 2013 21:22:19 +0000 (17:22 -0400)
Solaris' /bin/sh does not grok $(...), so use `...` instead.

Note that all recent versions of Solaris have included /bin/bash, but
I'm not sure the impact of using #!/bin/bash instead of #!/bin/sh on
some of our other platforms.

tests/script.test.sh
tests/subr.sh

index 6adfcf0..b209d96 100644 (file)
@@ -114,7 +114,7 @@ fi
 echo '(format t "Hello, Fasl~%")' > $tmpscript
 run_sbcl --eval "(compile-file \"$tmpscript\" :output-file \"$tmpfasl\")"  </dev/null >/dev/null
 chmod +x $tmpfasl
-SBCL_HOME=$(dirname $SBCL_CORE) ./$tmpfasl >$tmpout 2>$tmperr
+SBCL_HOME=`dirname $SBCL_CORE` ./$tmpfasl >$tmpout 2>$tmperr
 check_status_maybe_lose "--script exit status from fasl" $? 0 "(ok)"
 if [ -s $tmperr ] || [ "Hello, Fasl" != "`cat $tmpout`" ]
 then
index 2b63144..c1c5d49 100644 (file)
@@ -32,8 +32,8 @@ SBCL_RUNTIME="${TEST_SBCL_RUNTIME:-$SBCL_PWD/../src/runtime/sbcl}"
 SBCL_ARGS="${TEST_SBCL_ARGS:---noinform --no-sysinit --no-userinit --noprint --disable-debugger}"
 
 # Scripts that use these variables should quote them.
-TEST_BASENAME="`basename $0`"
-TEST_FILESTEM="$(basename "${TEST_BASENAME}" | sed -e 's/\.sh$//' -e 's/\./-/g')"
+TEST_BASENAME=`basename $0`
+TEST_FILESTEM=`basename "${TEST_BASENAME}" | sed -e 's/\.sh$//' -e 's/\./-/g'`
 : ${TEST_BASEDIR:="$SBCL_PWD"}
 TEST_DIRECTORY="${TEST_BASEDIR}/${TEST_FILESTEM}-$$"
 export TEST_DIRECTORY