Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen <guinevere@redhat.com>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH v6] gdb, configure: Add disable-formats option for configure
Date: Wed, 6 Aug 2025 10:53:38 -0300	[thread overview]
Message-ID: <6f40184b-9190-4597-a326-f62bb544d3b4@redhat.com> (raw)
In-Reply-To: <995b2448-6e30-4ba6-acb8-099b0723ee83@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1984 bytes --]

On 8/5/25 5:07 PM, Guinevere Larsen wrote:
>>> @@ -1952,11 +1970,17 @@ fi
>>>   # Note that WIN32APILIBS is set by GDB_AC_COMMON.
>>>   WIN32LIBS="$WIN32LIBS $WIN32APILIBS"
>>>   +# Object files to be used when building with support for all file 
>>> formats.
>>> +# This should not have elf or macho, as support for those formats 
>>> depends
>>> +# on BFD enabling them as well.
>>> +all_binary_file_srcs="\$(dbx_SRCS) \$(mips_SRCS) \$(coff_SRCS) 
>>> \$(xcoff_SRCS)"
>>> +
>>> +support_elf=no
>>>   # Add ELF support to GDB, but only if BFD includes ELF support.
>>>   GDB_AC_CHECK_BFD([for ELF support in BFD], gdb_cv_var_elf,
>>>                    [bfd_get_elf_phdr_upper_bound (NULL)], elf-bfd.h)
>>>   if test "$gdb_cv_var_elf" = yes; then
>>> -  CONFIG_OBS="$CONFIG_OBS elfread.o stap-probe.o dtrace-probe.o \
>>> +  CONFIG_OBS="$CONFIG_OBS stap-probe.o dtrace-probe.o \
>>>           gcore-elf.o elf-none-tdep.o"
>> Does it make sense (or is it useful) to compile these other files (other
>> than elfread.o) if ELF support is not enabled?  Could we just list them
>> all in elf_SRCS so that they are not built if the user doesn't want ELF
>> support?  If you don't have an ELF reader.
>
> I don't know. I took the path of least changes to implementing this, 
> made worse by me not having a convenient way to test a non-ELF target.
>
> I'll try to find a way to test if those are necessary and update the 
> patch if they aren't 

ah, turns out I could've just tried compiling with no elf support, oops. 
stap-probe and dtrace-probe can go

gcore-elf and elf-none-tdep are required to compile with 
--enable-targets=all, and since these aren't enough to consider elf 
supported, I think it's easier to just leave them here than figuring out 
which targets require them... I did notice that the arm-tdep.c does need 
them, but didn't go far into anything...

I'll submit a v7 with that update shortly

-- 
Cheers,
Guinevere Larsen
She/it

[-- Attachment #2: Type: text/html, Size: 3088 bytes --]

  reply	other threads:[~2025-08-06 13:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07 11:58 [PATCH v3] " 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
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 [this message]
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=6f40184b-9190-4597-a326-f62bb544d3b4@redhat.com \
    --to=guinevere@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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