From patchwork Mon Aug 31 18:51:40 2026 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Simon Marchi X-Patchwork-Id: 142545 Return-Path: X-Original-To: patchwork@sourceware.org Delivered-To: patchwork@sourceware.org Received: from vm01.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 497634BA7984 for ; Mon, 31 Aug 2026 18:53:38 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 497634BA7984 X-Original-To: gdb-patches@sourceware.org Delivered-To: gdb-patches@sourceware.org Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id 89FAD4BA2E30 for ; Mon, 31 Aug 2026 18:53:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 89FAD4BA2E30 Authentication-Results: sourceware.org; dmarc=fail (p=none dis=none) header.from=efficios.com Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=efficios.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 89FAD4BA2E30 Authentication-Results: sourceware.org; arc=none smtp.remote-ip=158.69.221.121 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1788202386; cv=none; b=mOnhlSaeWKHH27mMveVCVHq68A+oF5YlqjXePx06Q09+4X56Q+aKw+pK13G9WN82UMXyGtI6cGHrkfwW7NtESYTBmnQD4tkgKuAd51kc1H74piws4D4NFBvX2PgaUT1VYtVCDcWEyeGfp0tjPW0O+MHkDuNAn58cV15tfeDSpLQ= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1788202386; c=relaxed/simple; bh=QCdDzWZ0ckL2228E3bm0hfV4r0EzYUH6STnkGoB7DJo=; h=From:To:Subject:Date:Message-ID:MIME-Version; b=G8gbJAdOLlJPk7NYj4t6SHWUqmHVN0dXqAMnfpbogY5WOPSzXt7ZQQRE/PpIpMmhqJhp4BKMCdb6+0j7r19oN8/nwO9rle1DQQqhyKppe3P8NRLuDfkXuZS2f3IXENPs1yttCeU+F+sIdM4DCOwLmuB4uzt5HmOpT4uDBeFc2pc= ARC-Authentication-Results: i=1; sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 89FAD4BA2E30 Received: by simark.ca (Postfix) id F2D2C1E0A3; Mon, 31 Aug 2026 14:53:04 -0400 (EDT) From: Simon Marchi To: gdb-patches@sourceware.org Cc: Simon Marchi Subject: [PATCH 1/7] gdb: update README about the GNU make requirement Date: Mon, 31 Aug 2026 14:51:40 -0400 Message-ID: <20260831185300.572297-2-simon.marchi@efficios.com> X-Mailer: git-send-email 2.55.0 In-Reply-To: <20260831185300.572297-1-simon.marchi@efficios.com> References: <20260831185300.572297-1-simon.marchi@efficios.com> MIME-Version: 1.0 X-Spam-Status: No, score=-1165.8 required=5.0 tests=BAYES_00, GIT_PATCH_0, KAM_DMARC_NONE, KAM_DMARC_STATUS, LOCAL_AUTHENTICATION_FAIL_DMARC, LOCAL_AUTHENTICATION_FAIL_SPF, SPF_HELO_PASS, SPF_SOFTFAIL, TXREP shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces~patchwork=sourceware.org@sourceware.org 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 Reviewed-By: Eli Zaretskii --- gdb/README | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/gdb/README b/gdb/README index 492b0891668d..791bbd23b6c2 100644 --- a/gdb/README +++ b/gdb/README @@ -82,6 +82,9 @@ list of options, invoke the subdirectory `configure', like: (Take note of how this differs from the invocation used to actually configure the build tree.) + Building GDB requires GNU make version 3.82 or later; other `make' +programs will not work. + 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 @@ -254,10 +257,8 @@ Compiling GDB in another directory you need a different `gdb' compiled for each combination of host and target. `configure' is designed to make this easy by allowing you to generate each configuration in a separate subdirectory, rather than in -the source directory. If your `make' program handles the `VPATH' -feature correctly (GNU `make' and SunOS 'make' are two that should), -running `make' in each of these directories builds the `gdb' program -specified there. +the source directory. Running `make' in each of these directories +builds the `gdb' program specified there. To build `gdb' in a separate directory, run `configure' with the `--srcdir' option to specify where to find the source. (You also need @@ -367,8 +368,6 @@ more obscure GDB `configure' options are not listed here. `DIR'. `--srcdir=PATH' - *Warning: using this option requires GNU `make', or another `make' - that compatibly implements the `VPATH' feature.* Use this option to make configurations in directories separate from the GDB source directories. Among other things, you can use this to build (or maintain) several configurations simultaneously, @@ -778,8 +777,8 @@ When using a `make'-based method, you can use the Makefile variable make RUNTESTFLAGS=--directory=gdb.cp check -If you use GNU make, you can use its `-j' option to run the testsuite -in parallel. This can greatly reduce the amount of time it takes for +You can use the `-j' option of `make' to run the testsuite in +parallel. This can greatly reduce the amount of time it takes for the testsuite to run. In this case, if you set `RUNTESTFLAGS' then, by default, the tests will be run serially even under `-j'. You can override this and force a parallel run by setting the `make' variable