From: Matthias Klose <doko@ubuntu.com>
To: Nick Clifton <nickc@redhat.com>, Fangrui Song <i@maskray.me>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: Linker diagnostics for the incorrect options .
Date: Fri, 11 Dec 2020 11:25:26 +0100 [thread overview]
Message-ID: <43b3a4c2-af74-c177-fc9a-d198fd82a6e8@ubuntu.com> (raw)
In-Reply-To: <af5dda68-3ecc-e794-f29b-295aa523bc69@redhat.com>
On 9/23/20 11:31 AM, Nick Clifton via Binutils wrote:
> Hi Fangrui,
>
>> This is a conflict between the grouped short options syntax and single
>> dash prefixed long options.
>>
>> % touch an ommand ':)'
>> % ld.bfd -you -can -ofcourse -use -this -Long -command -Line ':)'
>> :)
>
> he!
>
>> For newer long options, we should encourage EXACTLY_TWO_DASHES
>
> Definitely.
>
>> (ld/lexsup.c). I have not seen grouped short options in a very large
>> code base and FreeBSD.
>> Maybe we can deprecate grouped short options syntax for ld.
>
> I like this idea. How about the attached patch ? With it applied I
> get output like this:
>
> % ld -vn -non-static -e 0 -v -e2 hello.o
> GNU ld (GNU Binutils) 2.35.50.20200923
> ld: Warning: grouped short command line options are deprecated: -vn
> ld: Error: unable to disambiguate: -non-static (did you mean --non-static ?)
>
> % echo $?
> 1
this causes PR ld/27050:
$ ld.bfd -no-pie
ld.bfd: Error: unable to disambiguate: -no-pie (did you mean --no-pie ?)
prev parent reply other threads:[~2020-12-11 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 5:29 Umesh Kalappa
2020-09-22 12:31 ` Nick Clifton
2020-09-22 18:40 ` Fangrui Song
[not found] ` <MWHPR12MB14567F315D72755B1CC41210CB3B0@MWHPR12MB1456.namprd12.prod.outlook.com>
2020-09-23 9:31 ` Nick Clifton
2020-10-02 0:19 ` Fangrui Song
[not found] ` <MWHPR12MB145628F1D93CC392F9F8F1DECB310@MWHPR12MB1456.namprd12.prod.outlook.com>
2020-10-05 12:55 ` Nick Clifton
2020-12-11 10:25 ` Matthias Klose [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=43b3a4c2-af74-c177-fc9a-d198fd82a6e8@ubuntu.com \
--to=doko@ubuntu.com \
--cc=binutils@sourceware.org \
--cc=i@maskray.me \
--cc=nickc@redhat.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).