From: Bruno Haible <bruno@clisp.org>
To: cygwin@cygwin.com
Subject: Re: fnmatch improvements
Date: Fri, 28 Jul 2023 12:56:27 +0200 [thread overview]
Message-ID: <24556977.snJFCo28Jb@nimes> (raw)
In-Reply-To: <ZMOCGyArlcmVAxI5@calimero.vinschen.de>
Corinna Vinschen wrote:
> After the above fail, I tried from scratch with your below patch,
> and I still get
>
> $ grep REPLACE_FNMATCH ./config.status
> S["REPLACE_FNMATCH"]="1"
>
> Even though
>
> $ grep fnmatch log1
> checking for fnmatch.h... yes
> checking for fnmatch... yes
> checking for working POSIX fnmatch... yes
>
> I'm quite puzzled.
It's sometimes hard to make incremental changes to generated files of the
GNU Build System plus Gnulib. I've therefore recreated a new tarball for you,
at https://haible.de/bruno/gnu/testdir-fnmatch.tar.gz .
The expected result is:
1. cd testdir-fnmatch-posix
./configure
grep REPLACE_FNMATCH config.status
(Expected: REPLACE_FNMATCH is 0)
make
make check
(Expected: No test failures)
cd ..
2. cd testdir-fnmatch-gnu
./configure
grep REPLACE_FNMATCH config.status
(Expected: REPLACE_FNMATCH is 1, because of FNM_EXTMATCH)
make
make check
(Expected: No test failures)
cd ..
Bruno
next prev parent reply other threads:[~2023-07-28 10:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 10:15 Bruno Haible
2023-07-27 18:24 ` Corinna Vinschen
2023-07-27 19:05 ` Corinna Vinschen
2023-07-27 20:25 ` Brian Inglis
2023-07-27 21:22 ` Bruno Haible
2023-07-27 22:17 ` Brian Inglis
2023-07-28 9:00 ` Corinna Vinschen
2023-07-28 9:53 ` Corinna Vinschen
2023-07-27 21:40 ` Bruno Haible
2023-07-28 8:53 ` Corinna Vinschen
2023-07-28 10:56 ` Bruno Haible [this message]
2023-07-28 11:14 ` Corinna Vinschen
2023-07-28 18:59 ` Corinna Vinschen
2023-07-28 19:33 ` Bruno Haible
2023-07-28 19:54 ` GB18030 locale Bruno Haible
2023-07-29 9:23 ` Corinna Vinschen
2023-07-29 9:53 ` Bruno Haible
2023-07-31 10:07 ` Corinna Vinschen
2023-07-31 13:38 ` Corinna Vinschen
2023-07-31 14:06 ` character class "alpha" Bruno Haible
2023-07-31 17:46 ` Corinna Vinschen
2023-07-31 18:20 ` Corinna Vinschen
2023-07-31 18:43 ` Bruno Haible
2023-07-31 21:12 ` Corinna Vinschen
2023-08-01 16:29 ` Brian Inglis
2023-08-02 7:56 ` Corinna Vinschen
2023-08-02 15:06 ` Corinna Vinschen
2023-07-31 21:13 ` Brian Inglis
2023-07-31 21:37 ` Bruno Haible
2023-07-28 11:12 ` fnmatch improvements Corinna Vinschen
2023-07-28 11:22 ` Bruno Haible
2023-07-28 21:42 ` Bill Stewart
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=24556977.snJFCo28Jb@nimes \
--to=bruno@clisp.org \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).