Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/README: Document GNU Make requirement
Date: Fri, 06 Mar 2026 09:11:59 +0200	[thread overview]
Message-ID: <86ikb9v3cw.fsf@gnu.org> (raw)
In-Reply-To: <8c97ede9-748c-4a70-9655-e0249d618094@redhat.com> (message from Guinevere Larsen on Thu, 5 Mar 2026 16:03:15 -0300)

> Date: Thu, 5 Mar 2026 16:03:15 -0300
> Cc: gdb-patches@sourceware.org
> From: Guinevere Larsen <guinevere@redhat.com>
> 
> On 3/5/26 3:56 PM, Eli Zaretskii wrote:
> >> From: Guinevere Larsen <guinevere@redhat.com>
> >> Cc: Guinevere Larsen <guinevere@redhat.com>
> >> Date: Thu,  5 Mar 2026 15:29:30 -0300
> >>
> >> User la_mettrie on IRC mentioned that they were having difficulties
> >> building GDB, and after some debugging, we figured out that they weren't
> >> using GNU Make. This is in the final documentation, but considering that
> >> it is not an obvious place to look, and the README mentions other build
> >> requirements, so this seems like a pretty obvious oversight.
> >> ---
> >>   gdb/README | 4 ++--
> >>   1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/gdb/README b/gdb/README
> >> index 492b0891668..09c88bcd19c 100644
> >> --- a/gdb/README
> >> +++ b/gdb/README
> >> @@ -86,8 +86,8 @@ configure the build tree.)
> >>   C++17 compiler for your system, you may be able to download and install
> >>   the GNU CC compiler.  It is available via anonymous FTP from the
> >>   directory `ftp://ftp.gnu.org/pub/gnu/gcc'.  GDB also requires an ISO
> >> -C standard library.  The GDB remote server, GDBserver, builds with some
> >> -non-ISO standard libraries - e.g. for Windows CE.
> >> +C standard library and GNU Make.  The GDB remote server, GDBserver,
> >> +builds with some non-ISO standard libraries - e.g. for Windows CE.
> > Thanks, but shouldn't this be much closer to the beginning of the
> > file, like where the build commands are first shown?  Mentioning that
> > here, so close to the end of the installation overview, sounds too
> > late.  People might overlook it.
> >
> That's a good point. I only put it here because it's where the other 
> build requirements were located, but I guess the entire paragraph should 
> be moved up. I will do that for v2, but while I'm at it, should we 
> really be teaching the user how to find a c++17 compiler? I think we 
> should remove the instructions on downloading GCC from the ftp 
> directory, and shorten the entire paragraph a bit, what do you think?

Yes, I think this part of README needs a serious restructuring.

  reply	other threads:[~2026-03-06  7:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 18:29 Guinevere Larsen
2026-03-05 18:56 ` Eli Zaretskii
2026-03-05 19:03   ` Guinevere Larsen
2026-03-06  7:11     ` Eli Zaretskii [this message]
2026-03-05 19:01 ` Andrew Pinski
2026-03-06  7:10   ` Eli Zaretskii
2026-03-06 12:13 ` [PATCH v2] gdb/README: Refactor where build requirements are explained Guinevere Larsen
2026-03-06 14:25   ` Eli Zaretskii
2026-03-06 16:43     ` Guinevere Larsen
2026-03-06 19:20       ` Eli Zaretskii
2026-03-09 14:28   ` [PATCH v3] " Guinevere Larsen
2026-03-09 14:51     ` Eli Zaretskii
2026-03-09 16:27       ` Guinevere Larsen
2026-03-09 16:41         ` Eli Zaretskii
2026-03-09 16:58           ` Pierre Muller

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=86ikb9v3cw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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