From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4296 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: fnmatch and FNM_CASEFOLD Date: Fri, 29 Nov 2013 12:42:49 -0500 Message-ID: <20131129174249.GC24286@brightrain.aerifal.cx> References: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1385746983 15284 80.91.229.3 (29 Nov 2013 17:43:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 29 Nov 2013 17:43:03 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4300-gllmg-musl=m.gmane.org@lists.openwall.com Fri Nov 29 18:43:09 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1VmS5s-0003UM-1M for gllmg-musl@plane.gmane.org; Fri, 29 Nov 2013 18:43:08 +0100 Original-Received: (qmail 13736 invoked by uid 550); 29 Nov 2013 17:43:05 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 13693 invoked from network); 29 Nov 2013 17:43:02 -0000 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:4296 Archived-At: On Fri, Nov 29, 2013 at 05:59:12PM +0800, orc wrote: > Hi list, > > This one really terrorized me well. Musl defines FNM_CASEFOLD in > fnmatch.h but really does nothing when this flag is passed to > function. This breaks busybox find -iname I believe, instead of file > list matching "Test" among with "test" i get only those which > contain "test" in their names with -iname "test". Missed lot of > files because of it. > Wishing this fixed or such define being removed. I think this is a reasonable request. FNM_CASEFOLD is problematic to support and I don't see adding it in the near/forseeable future. However I do wonder if we'd lose a lot of out-of-the-box compatibility relative to what we have now; in many cases, compiling without case-insensitive matching working might be preferable to not compiling at all. Is anyone willing to take up a task of checking which packages in pkgsrc or other 'supported' packages are using FNM_CASEFOLD unconditionally and how much work it would be to get patches upstream to make the use conditional on #ifdef FNM_CASEFOLD? Rich