Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen <guinevere@redhat.com>
To: gdb-patches@sourceware.org
Cc: Guinevere Larsen <guinevere@redhat.com>
Subject: [PATCH v2] gdb/README: Refactor where build requirements are explained
Date: Fri,  6 Mar 2026 09:13:03 -0300	[thread overview]
Message-ID: <20260306121303.2358881-1-guinevere@redhat.com> (raw)
In-Reply-To: <20260305182930.4119998-1-guinevere@redhat.com>

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.

This commit also shortens the entire paragraph that explains the build
requirements, and moves it closer to the start of the install
requirements, so that they are less likely to be missed by users.
---
 gdb/README | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/gdb/README b/gdb/README
index 492b0891668..8dc50667212 100644
--- a/gdb/README
+++ b/gdb/README
@@ -28,6 +28,10 @@ Configuration scripts and makefiles exist to cruise up and down this
 directory tree and automatically build all the pieces in the right
 order.
 
+   GDB requires a C++17 compiler, an ISO C standard library and GNU
+Make.  The GDB remote server, GDBserver, builds with some non-ISO
+standard libraries - e.g. for Windows CE.
+
    When you unpack the gdb-VERSION.tar.gz file, it will create a
 source directory called `gdb-VERSION'.
 
@@ -82,13 +86,6 @@ list of options, invoke the subdirectory `configure', like:
    (Take note of how this differs from the invocation used to actually
 configure the build tree.)
 
-   GDB requires a C++17 compiler.  If you do not have a
-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.
-
    GDB can optionally be built against various external libraries.
 These dependencies are described below in the "`configure options"
 section of this README.

base-commit: e4fe38115fea0a9f357527959893f18ca8d51a03
-- 
2.53.0


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

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 18:29 [PATCH] gdb/README: Document GNU Make requirement 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
2026-03-06  7:10   ` Eli Zaretskii
2026-03-06 12:13 ` Guinevere Larsen [this message]
2026-03-06 14:25   ` [PATCH v2] gdb/README: Refactor where build requirements are explained 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=20260306121303.2358881-1-guinevere@redhat.com \
    --to=guinevere@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