summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPádraig Brady <P@draigBrady.com>2026-01-18 12:48:36 +0000
committerPádraig Brady <P@draigBrady.com>2026-01-18 12:48:36 +0000
commitfcaa3a39c76c204cdaddca89e665ebef51ccfaff (patch)
tree60abb2797a1b692a167b09b0e5162193d11ea8ca
parent0d5b66ca669436893cb3d3b8fcd7a3b16ec0dc5d (diff)
downloadcoreutils-fcaa3a39c76c204cdaddca89e665ebef51ccfaff.tar.gz
coreutils-fcaa3a39c76c204cdaddca89e665ebef51ccfaff.zip
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.
-rwxr-xr-xtests/misc/coreutils.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/misc/coreutils.sh b/tests/misc/coreutils.sh
index a554be090..5cf5fce69 100755
--- 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