From: Andrew Pinski <pinskia@gmail.com>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/README: Document GNU Make requirement
Date: Thu, 5 Mar 2026 11:01:34 -0800 [thread overview]
Message-ID: <CA+=Sn1ma_SED=GAnmmYtj18Yd3oSa6P82JKwopmaB6LDR6E91Q@mail.gmail.com> (raw)
In-Reply-To: <20260305182930.4119998-1-guinevere@redhat.com>
On Thu, Mar 5, 2026 at 10:30 AM Guinevere Larsen <guinevere@redhat.com> wrote:
>
> 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.
Hmm, I thought there was another seperate installation guide for gdb
but nope the README is it.
Eli's comment is correct but that is really about refactoring the
whole README really because the mentioning of requiring a C++17
compiler should be at the same location as requring GNU make.
Thanks,
Andrew Pinski
> ---
> 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.
>
> GDB can optionally be built against various external libraries.
> These dependencies are described below in the "`configure options"
>
> base-commit: 7c5179caca8cbca0f2fdb64f0fe215cee803ccb3
> prerequisite-patch-id: 47ca70553d73d20b7f4c648078529a2bb301eb64
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-03-05 19:02 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
2026-03-05 19:01 ` Andrew Pinski [this message]
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='CA+=Sn1ma_SED=GAnmmYtj18Yd3oSa6P82JKwopmaB6LDR6E91Q@mail.gmail.com' \
--to=pinskia@gmail.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