From: Guinevere Larsen <guinevere@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] gdb, configure: Add disable-formats option for configure
Date: Mon, 7 Apr 2025 14:48:45 -0300 [thread overview]
Message-ID: <296b9f38-16ef-4488-ba5a-58394bde1fbb@redhat.com> (raw)
In-Reply-To: <87wmc1173c.fsf@tromey.com>
[-- Attachment #1: Type: text/plain, Size: 1725 bytes --]
On 4/3/25 2:35 PM, Tom Tromey wrote:
>>>>>> "Guinevere" == Guinevere Larsen<guinevere@redhat.com> writes:
> Guinevere> GDB has support for many binary file formats, some which might be very
> Guinevere> unlikely to be found in some situations (such as the COFF format in
> Guinevere> linux). This commit introduces the option for a user to choose which
> Guinevere> formats GDB will support at build configuration time.
>
> Guinevere> +* Configure changes
> Guinevere> +
> Guinevere> +enable-binary-file-formats=[FORMAT,...]
> Guinevere> +enable-binary-file-formats=all
>
> Add the leading "--" here?
> I didn't look to see what other NEWS entries do.
I double checked the other NEWS entries, and you're right, I should add
"--" to the option.
> Guinevere> +# Object files to be used when building with support for all file formats.
> Guinevere> +all_binary_format_obs="dbxread.o mipsread.o coffread.o coff-pe-read.o xcoffread.o"
>
> I would much rather have this kind of information in the Makefile. I
> know gdb doesn't always do that right now -- but the current way is kind
> of bad IMO.
>
> We can use GNU make features, so it's not hard to transform a list of
> formats like "elf xcoff" into a list of variable references like
> "$(elf_OBJS) $(xcoff_OBJS)"
I'm fine with changing this. I'm only unsure what GNU make feature you
mean. I suppose you mean the makefile should have:
elf_OBJS=elfread.c
xcoff_OBJS=xcoff.c
all_format_OBJS="$(elf_OBJS) $(xcoff_OBJS) ..."
and there is some way to parse --enable-binary-file-formats in the makefile?
>
> Guinevere> diff --git a/gdb/configure.format b/gdb/configure.format
>
> Then we wouldn't need this file, either.
>
> Tom
>
--
Cheers,
Guinevere Larsen
She/Her/Hers
[-- Attachment #2: Type: text/html, Size: 2906 bytes --]
next prev parent reply other threads:[~2025-04-07 17:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 11:58 Guinevere Larsen
2025-03-07 12:09 ` Eli Zaretskii
2025-03-07 12:49 ` Guinevere Larsen
2025-03-07 13:03 ` Eli Zaretskii
2025-03-27 20:21 ` [PING][PATCH " Guinevere Larsen
2025-04-03 17:35 ` [PATCH " Tom Tromey
2025-04-07 17:48 ` Guinevere Larsen [this message]
2025-04-07 19:23 ` Tom Tromey
2025-04-08 13:47 ` [PATCH v4] " Guinevere Larsen
2025-04-08 14:06 ` Andreas Schwab
2025-04-08 14:24 ` Guinevere Larsen
2025-04-08 14:44 ` Andreas Schwab
2025-05-26 17:11 ` [PATCH v5 1/1] " Guinevere Larsen
2025-07-07 20:16 ` [PATCH v6] " Guinevere Larsen
2025-07-31 18:42 ` [PING][PATCH " Guinevere Larsen
2025-08-05 16:03 ` [PATCH " Simon Marchi
2025-08-05 19:06 ` Eli Zaretskii
2025-08-05 19:36 ` Simon Marchi
2025-08-05 20:07 ` Guinevere Larsen
2025-08-06 13:53 ` Guinevere Larsen
2025-08-06 14:17 ` [PATCH v7 1/1] gdb, configure: Add enable-binary-file-format " Guinevere Larsen
2025-08-14 15:39 ` Tom Tromey
2025-08-14 16:23 ` Guinevere Larsen
2025-05-27 11:32 ` [PATCH v3] gdb, configure: Add disable-formats " Pedro Alves
2025-05-27 16:26 ` 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=296b9f38-16ef-4488-ba5a-58394bde1fbb@redhat.com \
--to=guinevere@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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