mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Felix Janda <felix.janda@posteo.de>
To: musl@lists.openwall.com
Subject: Re: fnmatch and FNM_CASEFOLD
Date: Sun, 1 Dec 2013 15:02:35 +0100	[thread overview]
Message-ID: <20131201140235.GA3383@gauss> (raw)
In-Reply-To: <20131130211612.GX24286@brightrain.aerifal.cx>

Rich Felker wrote:
> On Fri, Nov 29, 2013 at 06:34:17PM -0500, Rich Felker wrote:
[...]
> > I'd also like to remove FNM_LEADING_DIR, which is unsupported by musl
> > and documented in the man page as:
> > 
> >     "This flag is mainly for the internal use of glibc and is
> >     implemented only in certain cases."
> 
> Unfortunately, Debian codesearch is showing a lot of hits for
> FNM_LEADING_DIR; I haven't researched whether they're hard or soft
> dependencies, so if anyone is willing to look into that, it'd be
> helpful. See: http://codesearch.debian.net/search?q=FNM_LEADING_DIR

The vast majority of the matches comes from code copied from gnulib,...
implementing fnmatch().

busybox's tar uses it if available for the -X and -T option for file
in/exclusion.

Jane Street's core library for OCaml provides libc's version of
fnmatch() to its users. Its implementation expects FNM_LEADING_DIR
(and also FNM_CASE_FOLD) to exists.

recoll will only use FNM_LEADING_DIR if it is available. However its
documentation says it is always used.

csync2 and dds2tar use the flag unconditionally.

sitecopy checks in its config script for the existance of FNM_LEADING_DIR
and uses it if declared. It is therefore currently broken for musl and
fixed if one removes the declaration.

Felix


  reply	other threads:[~2013-12-01 14:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29  9:59 orc
2013-11-29 17:42 ` Rich Felker
2013-11-29 23:34   ` Rich Felker
2013-11-30 21:16     ` Rich Felker
2013-12-01 14:02       ` Felix Janda [this message]
2013-12-01 22:06         ` Rich Felker
2013-12-02  7:26           ` Rich Felker

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=20131201140235.GA3383@gauss \
    --to=felix.janda@posteo.de \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).