From: Tom Tromey <tom@tromey.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] sim, sim/m32c, sim/rl78: Use getopt_long
Date: Tue, 25 Oct 2022 13:42:22 -0600 [thread overview]
Message-ID: <87mt9jbsgx.fsf@tromey.com> (raw)
In-Reply-To: <45f95875-667a-3f63-db4c-2d135cb9bfe9@irq.a4lg.com> (Tsukasa OI's message of "Wed, 26 Oct 2022 02:17:10 +0900")
> I've described it in the commit message of PATCH v2.
> <https://sourceware.org/pipermail/gdb-patches/2022-October/193115.html>
I see, thank you. This makes me appreciate your view better.
libiberty is funny because it requires certain configure checks and
definitions but doesn't provide a simple way to do them. gdb has
libiberty.m4 but it is incomplete -- for example it doesn't do this
getopt check.
Something more robust would probably end up looking like gnulib... which
does have a getopt module, but which we don't use. (And binutils
doesn't use gnulib at all.)
Anyway. Switching to getopt_long seems like a fine workaround.
Programs should be using it anyway so that --help and --version can be
implemented.
Tom
next prev parent reply other threads:[~2022-10-25 19:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3b7e769f-b5e9-4049-786f-d00d997f0280@irq.a4lg.com>
2022-10-18 17:13 ` Tsukasa OI
2022-10-21 16:27 ` Tom Tromey
2022-10-24 7:51 ` Tsukasa OI
2022-10-25 5:53 ` Tsukasa OI
2022-10-25 16:54 ` Tom Tromey
2022-10-25 17:17 ` Tsukasa OI
2022-10-25 19:42 ` Tom Tromey [this message]
2022-10-25 6:27 ` [PATCH v2] sim, sim/{m32c,ppc,rl78}: " Tsukasa OI
2022-10-26 8:59 ` Mike Frysinger
2022-10-26 10:57 ` Tsukasa OI
2022-10-26 16:01 ` Mike Frysinger
2022-10-27 1:29 ` Tsukasa OI
2022-10-26 10:59 ` [PATCH v3] " Tsukasa OI
2022-10-27 1:23 ` [PATCH v4] " Tsukasa OI
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=87mt9jbsgx.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=research_trasio@irq.a4lg.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).