From: Tom Tromey <tom@tromey.com>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb, configure: Add disable-formats option for configure
Date: Fri, 27 Sep 2024 12:01:15 -0600 [thread overview]
Message-ID: <878qvdht78.fsf@tromey.com> (raw)
In-Reply-To: <f5bb752d-ad8f-46f6-b042-06e351280d12@redhat.com> (Guinevere Larsen's message of "Thu, 26 Sep 2024 16:49:39 -0300")
>>>>> "Guinevere" == Guinevere Larsen <guinevere@redhat.com> writes:
>>> +enable-formats=[FORMAT,]...
>> I think this option name is too generic.
Guinevere> Eli suggested objfile-format and binary-file-format. I was planning on
Guinevere> using the former, unless you still think is too generic, or have a
Guinevere> better suggestion :)
I don't believe naming things is really my strong suit.
I tend to rush through it.
"objfile" though seems like gdb internals terminology.
Maybe something like "--enable-gdb-file-formats"?
Having "gdb" in there explicitly may make it more clear that this isn't
affecting BFD.
Guinevere> I guess the real problem is a confusing name (and
Guinevere> overlap). All_target_formats is all the formats that have to be
Guinevere> compiled in if the user requested --enable-targets=all. This list
Guinevere> doesn't have Mach-O and dbx.
dbx I understand, since a.out is largely dead, but surely Mach-O is
needed by --enable-targets=all in order to target macOS?
Tom
next prev parent reply other threads:[~2024-09-27 18:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 17:53 Guinevere Larsen
2024-09-26 5:49 ` Eli Zaretskii
2024-09-26 18:16 ` Guinevere Larsen
2024-09-26 18:35 ` Eli Zaretskii
2024-09-26 21:03 ` Guinevere Larsen
2024-09-27 6:05 ` Eli Zaretskii
2024-10-02 13:25 ` Andrew Burgess
2024-10-02 14:15 ` Eli Zaretskii
2024-10-04 14:26 ` Andrew Burgess
2024-10-04 14:45 ` Eli Zaretskii
2024-10-07 18:30 ` Guinevere Larsen
2024-10-07 19:17 ` Eli Zaretskii
2024-10-07 19:58 ` Guinevere Larsen
2024-10-08 11:44 ` Eli Zaretskii
2024-10-08 13:03 ` Guinevere Larsen
2024-10-08 13:21 ` Eli Zaretskii
2024-10-10 14:45 ` Guinevere Larsen
2024-10-10 16:10 ` Andrew Burgess
2024-09-26 19:18 ` Tom Tromey
2024-09-26 19:49 ` Guinevere Larsen
2024-09-27 18:01 ` Tom Tromey [this message]
2024-10-02 13:56 ` Andrew Burgess
2024-10-02 20:37 ` Guinevere Larsen
2024-10-03 10:15 ` Andrew Burgess
2024-10-04 14:49 ` Andrew Burgess
2024-10-10 20:18 ` Guinevere Larsen
2024-10-16 10:50 ` Andrew Burgess
2024-10-16 21:00 ` Guinevere Larsen
2024-10-17 19:43 ` Tom Tromey
2024-10-17 19:48 ` Guinevere Larsen
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=878qvdht78.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@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