Previously, the 'second' test would test against `/bin/bash` instead of against the bash in the testfile archive. That looks unintentional: it seems the test is intended to prove sysroot can follow symlinks, but otherwise is meant to be self-contained and not supposed to depend on what /bin/bash happens to look like on the system where the test is ran.
Signed-off-by: Arnout Engelen <[email protected]> --- tests/run-sysroot.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/run-sysroot.sh b/tests/run-sysroot.sh index fe302446..8cdbce0f 100755 --- a/tests/run-sysroot.sh +++ b/tests/run-sysroot.sh @@ -54,7 +54,7 @@ if [[ "$HAVE_OPENAT2" = 1 ]]; then rm -f "${tmpdir}/sysroot/bin" mkdir "${tmpdir}/sysroot/bin" mv "${tmpdir}/sysroot/usr/bin/bash" "${tmpdir}/sysroot/bin/bash" - ln -s /bin/bash "${tmpdir}/sysroot/usr/bin/bash" + ln -s "${tmpdir}/sysroot/bin/bash" "${tmpdir}/sysroot/usr/bin/bash" # Check that stack with --sysroot generates correct backtrace even if target # binary is actually absolute symlink pointing outside of sysroot directory -- 2.51.2
