Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/7] gdb: update README about the GNU make requirement
Date: Tue, 01 Sep 2026 15:26:16 +0300	[thread overview]
Message-ID: <86wlt56tuf.fsf@gnu.org> (raw)
In-Reply-To: <20260831185300.572297-2-simon.marchi@efficios.com> (message from Simon Marchi on Mon, 31 Aug 2026 14:51:40 -0400)

> From: Simon Marchi <simon.marchi@efficios.com>
> Cc: Simon Marchi <simon.marchi@efficios.com>
> Date: Mon, 31 Aug 2026 14:51:40 -0400
> 
> The README still suggests that GDB can be built with a make other than GNU
> make, which is not the case since 2016 (f2ff9acd32b4 "Document new hard
> requirement on GNU make").
> 
> The manual already lists GNU make in the requirements:
> 
>     GNU make
>         GDB's build system relies on features only found in the GNU make
>         program.  Other variants of make will not work.
> 
> and the minimum version is documented in gdb/NEWS:
> 
>     * Building GDB and GDBserver now requires GNU make >= 3.82.
> 
> Bring the README in line with that.
> 
>  - Mention the GNU make requirement, including the minimum version, near
>    where we also state the C++17 compiler requirement.
> 
>  - Drop the "if your make program handles the VPATH feature correctly"
>    part from the "Compiling GDB in another directory" section.
> 
>  - Drop the warning about --srcdir requiring GNU make.
> 
>  - Drop the "If you use GNU make" conditional from the paragraph about
>    running the testsuite in parallel.
> 
> Change-Id: I5c0387d977ab87069c01c0249c51b2f30318a0c7
> ---
>  gdb/README | 15 +++++++--------
>  1 file changed, 7 insertions(+), 8 deletions(-)

Thanks, this is okay.

Reviewed-By: Eli Zaretskii <eliz@gnu.org>

  reply	other threads:[~2026-09-01 12:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31 18:51 [PATCH 0/7] Some Makefile cleanups Simon Marchi
2026-08-31 18:51 ` [PATCH 1/7] gdb: update README about the GNU make requirement Simon Marchi
2026-09-01 12:26   ` Eli Zaretskii [this message]
2026-09-01 13:36     ` Simon Marchi
2026-08-31 18:51 ` [PATCH 2/7] gdb, gdbserver: require gcc-style dependency generation, drop the depcomp fallback Simon Marchi
2026-09-01 16:32   ` Tom Tromey
2026-09-01 20:16     ` Simon Marchi
2026-09-02  7:37       ` Rainer Orth
2026-09-02 12:26         ` Simon Marchi
2026-08-31 18:51 ` [PATCH 3/7] gdbserver: fix missing dependency tracking for gdbreplay.o Simon Marchi
2026-09-01 16:33   ` Tom Tromey
2026-08-31 18:51 ` [PATCH 4/7] gdb, gdbserver: always use order-only prerequisites for generated files Simon Marchi
2026-09-01 16:34   ` Tom Tromey
2026-08-31 18:51 ` [PATCH 5/7] gdb, gdbserver: remove the .NOEXPORT target Simon Marchi
2026-09-01 16:37   ` Tom Tromey
2026-08-31 18:51 ` [PATCH 6/7] gdb: remove the explicit ada-exp.o rule Simon Marchi
2026-09-01 16:38   ` Tom Tromey
2026-08-31 18:51 ` [PATCH 7/7] gdb, gdbserver: create the dependency directories from the Makefiles Simon Marchi
2026-09-01 16:47   ` Tom Tromey
2026-09-01 20:18     ` Simon Marchi
2026-09-01 20:37       ` Simon Marchi
2026-09-02 18:36         ` Tom Tromey
2026-09-03 13:45           ` Simon Marchi

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=86wlt56tuf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.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