Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [GDB 18] gdb/configure: fix string quoting in AC_MSG_WARN and AC_MSG_ERROR
Date: Tue, 11 Aug 2026 16:35:20 +0300	[thread overview]
Message-ID: <86bjb8ye3r.fsf@gnu.org> (raw)
In-Reply-To: <14328877dfdc53dcfad582dd2b56861dc92396fd.1786453193.git.aburgess@redhat.com> (message from Andrew Burgess on Tue, 11 Aug 2026 14:02:06 +0100)

> From: Andrew Burgess <aburgess@redhat.com>
> Cc: Eli Zaretskii <eliz@gnu.org>,
> 	Andrew Burgess <aburgess@redhat.com>
> Date: Tue, 11 Aug 2026 14:02:06 +0100
> 
> If / when approve I plan to push this to both master and gdb-18-branch.

Thanks.  I have a question about this below.

> Now when configuring with
> --enable-binary-file-formats='coff,xcoff,elf,macho' on a target that
> doesn't support Mach-O, e.g. GNU/Linux, the configure will stop like
> this:
> 
>   checking for ELF support in BFD... yes
>   checking for library containing dlopen... (cached) none required
>   checking for Mach-O support in BFD... no
>   configure: error: Mach-O support was requested, but BFD does not support it
>   make: *** [Makefile:13461: configure-gdb] Error 1

Hmm... so building with Mach-O support on GNU/Linux and MS-Windows is
not possible at all?  I'm not sure I understand the "BFD does not
support it" part of the error message: shouldn't BFD that is compiled
as part of GDB be configured to support Mach-O when GDB is configured
with --enable-binary-file-formats='coff,xcoff,elf,macho'?  Or what am
I missing?

Thanks.

  reply	other threads:[~2026-08-11 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11 13:02 Andrew Burgess
2026-08-11 13:35 ` Eli Zaretskii [this message]
2026-08-11 16:33   ` Andrew Burgess
2026-08-12 19:02     ` Guinevere Larsen
2026-08-12 19:55 ` Tom Tromey
2026-08-13  9:08   ` Andrew Burgess
2026-08-13 12:21     ` Eli Zaretskii

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=86bjb8ye3r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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