aboutsummaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorRon Yorston <rmy@pobox.com>2026-02-01 09:29:44 +0000
committerRon Yorston <rmy@pobox.com>2026-02-01 09:29:44 +0000
commite27f759c63b338e6e6cf6dc8d9d0711e9c05d6a5 (patch)
treefa5987a920e978603c2fad778e056f7a76b89a2b /scripts
parent7f32f25ba1652f799e9e7ffe756dcee08c710e70 (diff)
downloadbusybox-w32-e27f759c63b338e6e6cf6dc8d9d0711e9c05d6a5.tar.gz
busybox-w32-e27f759c63b338e6e6cf6dc8d9d0711e9c05d6a5.tar.bz2
busybox-w32-e27f759c63b338e6e6cf6dc8d9d0711e9c05d6a5.zip
libbb: fix regression where 'which' output duplicate slashesHEADmaster
If an element of $PATH had a trailing slash 'which' displayed two slashes when an executable was found in that directory. This is a regression caused by upstream commit 49d9e06fb (libbb: modify find_executable() to not temporarily write to PATH). Prior to this commit find_executable() used concat_path_file() to build the path of the executable. This avoids including duplicate slashes in its output. The new code didn't. Add a test in find_executable() to detect the problem. It still fails if there are multiple trailing slashes. Don't do that. Adds 48 bytes.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions