aboutsummaryrefslogtreecommitdiff
path: root/runit
diff options
context:
space:
mode:
authorRon Yorston <rmy@pobox.com>2022-06-23 16:05:17 +0100
committerRon Yorston <rmy@pobox.com>2022-06-23 16:05:17 +0100
commit6c19fb9008e2dcd7a2d4ce42f618ec2079b1230f (patch)
tree0b6694dbc72da8e77bcc679ba8235607f91261d5 /runit
parent31467ddfcbbc433ed9ceff2eae2a359d0ca1e6d5 (diff)
downloadbusybox-w32-6c19fb9008e2dcd7a2d4ce42f618ec2079b1230f.tar.gz
busybox-w32-6c19fb9008e2dcd7a2d4ce42f618ec2079b1230f.tar.bz2
busybox-w32-6c19fb9008e2dcd7a2d4ce42f618ec2079b1230f.zip
win32: bug fix in fnmatch(3)
A user reports: Here is the shell script that causes me problems: var=foo:bar echo ${var#*[[:space:]]} What expect I to see echoed is foo:bar, however what I see bar. It seems that the [[:space:]] character class is matching the colon character in addition to whitespace characters. I see the same problem with the [[:blank:]] character class. This is due to a bug in the WIN32 implementation of fnmatch(3) which is derived from an old snapshot of glibc code (glibc commit 7814856974 from 1999-09-12). The bug was fixed in glibc by commit 83b1b6d8fa of 2000-07-04. Apply the equivalent fix to our version.
Diffstat (limited to 'runit')
0 files changed, 0 insertions, 0 deletions