From: Andrey Repin <anrdaemon@yandex.ru>
To: Houder <cygwin@cygwin.com>, cygwin@cygwin.com
Subject: Re: util-linux: getopt: broken --name option for a while now
Date: Fri, 07 Dec 2018 17:35:00 -0000 [thread overview]
Message-ID: <543338755.20181207203024@yandex.ru> (raw)
In-Reply-To: <e8f4f432b50594f79ae13f2758ec64cf@smtp-cloud7.xs4all.net>
Greetings, Houder!
> On Fri, 7 Dec 2018 02:56:50, Andrey Repin wrote:
>> Greetings, All!
>>
>> This has been plaguing me for several years, but only now I got to test it
>> more thoroughly.
>> Shame on me.
>>
>> $ /usr/bin/getopt --options '+H' --shell sh --name x -- -d
>> getopt: unknown option -- d
>>
>> Expected output:
>> x: unknown option -- d
>>
>> $ /usr/bin/getopt -V
>> getopt from util-linux 2.25.2
>>
>> Poked around,
>> getopt from 2.20.1, 2.27.1, 2.31.1 and (reportedly)2.33 works as expected.
> 2.27.1? Typo?
No, just a different OS.
# lsb_release -a; /usr/bin/getopt -V; /usr/bin/getopt --options '+H' --shell sh --name x -- -d
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial
getopt from util-linux 2.27.1
x: invalid option -- 'd'
--
> See:
> https://stackoverflow.com/questions/43078330/how-to-use-the-name-argument-to-getopt
> ( How to use the --name argument to getopt? )
> "This is a bug (or just a non-portability issue) which is already fixed in
> util-linux 2.28, by commit 30fbf2f6. Before this fix it worked only on Linux,
That explains it.
> OSX and a few BSD flavors but not on WIN32 or GNU-Hurd for example".
> The answer by "rudimeier" also decribes a temporary work-around.
--
With best regards,
Andrey Repin
Friday, December 7, 2018 20:24:07
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2018-12-07 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 0:05 Andrey Repin
2018-12-07 10:31 ` Houder
2018-12-07 17:35 ` Andrey Repin [this message]
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=543338755.20181207203024@yandex.ru \
--to=anrdaemon@yandex.ru \
--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).