From: tavianator <tavianator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] bfs: update to 2.4.
Date: Fri, 25 Feb 2022 16:22:58 +0100 [thread overview]
Message-ID: <20220225152258.swdo055YhJ3rjnxwFVu090W9D-kZddmCBJSpD2ylEx8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35836@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
New comment by tavianator on void-packages repository
https://github.com/void-linux/void-packages/pull/35836#issuecomment-1050947339
Comment:
The musl failure is a bug in musl I think. POSIX says this about `fnmatch()`:
> If pattern ends with an unescaped <backslash>, fnmatch() shall return a non-zero value (indicating either no match or an error).
And yet:
```
$ cat foo.c
#include <assert.h>
#include <fnmatch.h>
int main(void) {
assert(fnmatch("\\", "\\", 0) != 0);
return 0;
}
$ gcc foo.c -o foo && ./foo
$ musl-gcc foo.c -o foo && ./foo
Assertion failed: fnmatch("\\", "\\", 0) != 0 (foo.c: main: 5)
```
next prev parent reply other threads:[~2022-02-25 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 21:36 [PR PATCH] " daniel-eys
2022-02-24 21:57 ` daniel-eys
2022-02-25 15:22 ` tavianator [this message]
2022-03-27 18:33 ` [PR PATCH] [Updated] [WIP] " daniel-eys
2022-03-27 20:33 ` [PR PATCH] [Merged]: bfs: update to 2.5 leahneukirchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220225152258.swdo055YhJ3rjnxwFVu090W9D-kZddmCBJSpD2ylEx8@z \
--to=tavianator@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).