diff options
| author | Ron Yorston <rmy@pobox.com> | 2022-10-26 11:47:42 +0100 |
|---|---|---|
| committer | Ron Yorston <rmy@pobox.com> | 2022-10-26 11:47:42 +0100 |
| commit | d71cb67ff91762ae78e87440b87d7c9a160b2937 (patch) | |
| tree | e378f71776199ff4fe44cb3bc020a8f43278bd2b /arch | |
| parent | 0b5bd6e1436c38a74c5294535d5f4d7a7cf79d54 (diff) | |
| download | busybox-w32-d71cb67ff91762ae78e87440b87d7c9a160b2937.tar.gz busybox-w32-d71cb67ff91762ae78e87440b87d7c9a160b2937.tar.bz2 busybox-w32-d71cb67ff91762ae78e87440b87d7c9a160b2937.zip | |
win32: revert special treatment of Unix-style absolute paths
Commit 605972390 (win32: handle Unix-style absolute paths for
executables) added special treatment of paths for executables
starting with a slash. Such paths are absolute on Unix but are
relative to the current drive on Windows. On reflection this
commit did more than necessary. Later commits provided special
treatment only for paths starting with locations traditionally
used to contain binaries on Unix. This is probably sufficient.
Problems introduced by commit 605972390 include:
- If the current drive isn't the system drive tab completion of a
command starting with a slash confusingly references the system
drive.
- Building busybox-w32 with w64devkit fails on drives other than
the system drive.
Revert the changes introduced by commit 605972390.
This saves 192 bytes.
(GitHub issue #239)
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions