From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/7523 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: getopt_long incompatibility Date: Mon, 27 Apr 2015 12:18:16 -0400 Message-ID: <20150427161816.GY17573@brightrain.aerifal.cx> References: <20150427062432.GA30394@mforney.org> 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 1430151530 21780 80.91.229.3 (27 Apr 2015 16:18:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 27 Apr 2015 16:18:50 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-7536-gllmg-musl=m.gmane.org@lists.openwall.com Mon Apr 27 18:18:46 2015 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1Ymljs-00050S-NU for gllmg-musl@m.gmane.org; Mon, 27 Apr 2015 18:18:32 +0200 Original-Received: (qmail 24251 invoked by uid 550); 27 Apr 2015 16:18:30 -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 24233 invoked from network); 27 Apr 2015 16:18:29 -0000 Content-Disposition: inline In-Reply-To: <20150427062432.GA30394@mforney.org> User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:7523 Archived-At: On Sun, Apr 26, 2015 at 11:24:32PM -0700, Michael Forney wrote: > Hi, > > I noticed when building gzip with musl that gnulib is still replacing > getopt and getopt_long. After some investigation, it looks to be because > it expects getopt_long to accept ambiguous options with the same > has_arg, flag, and val values[0]. > > The code responsible for this seems to only do this for getopt_long and > not getopt_long_only[1]. I have no idea why, but since musl aims to > conform to glibc's getopt_long behavior, we should probably do the same. > > [0] http://git.savannah.gnu.org/cgit/gnulib.git/tree/m4/getopt.m4#n313 > [1] http://sourceware.org/git/?p=glibc.git;a=blob;f=posix/getopt.c;hb=HEAD#l562 I read the gnulib code but I don't see why it expects a match. From the glibc code it looks to me like the ambig_list should have length 2 and produce an error. I don't see any reasonable way getopt_long could choose between the two choices for the user without violating a principle of least surprise. Do you get what's going on? Rich