tests: use `command -v` to identify binary

* tests/misc/coreutils.sh: Be more flexibile by using `command -v`
to identify the binary to be executed, rather than linking
directly to the built binary.

diff --git a/tests/misc/coreutils.sh b/tests/misc/coreutils.sh
index a554be090b7df275c3e93fab6cbd0b1d331790a4..5cf5fce6985d379dbaf31559606a7380ddc4e5bc 100755 (executable)
--- a/tests/misc/coreutils.sh
+++ b/tests/misc/coreutils.sh
@@ -34,7 +34,7 @@ echo "coreutils: unknown program 'blah'" > exp || framework_failure_
 returns_ 1 coreutils --coreutils-prog='blah' --help 2>err || fail=1
 compare exp err || fail=1
 
-ln -s $abs_top_builddir/src/coreutils$EXEEXT blah || framework_failure_
+ln -s "$(command -v coreutils)" blah || framework_failure_
 returns_ 1 ./blah 2>err || fail=1
 compare exp err || fail=1
 returns_ 1 ./blah --version 2>err || fail=1