public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: gdb-patches@sourceware.org, nd@arm.com
Subject: Re: [PATCH] Require GNU make 3.82
Date: Thu, 18 Jul 2019 06:17:00 -0000	[thread overview]
Message-ID: <83v9vzyih8.fsf@gnu.org> (raw)
In-Reply-To: <20190715101124.77677-1-alan.hayward@arm.com> (message from Alan	Hayward on Mon, 15 Jul 2019 10:11:29 +0000)

> From: Alan Hayward <Alan.Hayward@arm.com>
> CC: nd <nd@arm.com>, Alan Hayward <Alan.Hayward@arm.com>
> Date: Mon, 15 Jul 2019 10:11:29 +0000
> 
> Gdbserver has failed to build with GNU make 3.81 since commit 08f10e02be.

Which feature of Make 3.82 and later is required to successfully
build gdbserver?

> diff --git a/gdb/NEWS b/gdb/NEWS
> index 4e479bf738..3a92b24e44 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -251,6 +251,11 @@ maint show test-options-completion-result
>    GDB) in the output directory for each test script.  Multiple invocations
>    are appended with .1, .2, .3 etc.
>  
> +* Building GDB and GDBserver now requires GNU make >= 3.82.
> +
> +  Using another implementation of the make program or an earlier version of
> +  GNU make to build GDB or GDBserver is not supported.
> +

The test is OK, thanks.

  parent reply	other threads:[~2019-07-18  6:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15 10:11 Alan Hayward
2019-07-16  0:51 ` Kevin Buettner
2019-07-16 10:36   ` Alan Hayward
2019-07-18  6:17 ` Eli Zaretskii [this message]
2019-07-18 10:00   ` Eli Zaretskii
2019-07-18 10:57   ` Alan Hayward
2019-08-01 16:09     ` Alan Hayward
2020-07-14 14:30     ` Tom de Vries
2020-07-15  7:46       ` Tom de Vries
2020-07-15 17:14         ` Kevin Buettner
2020-07-15 17:31           ` Tom de Vries
2020-07-15 19:14             ` Kevin Buettner
2020-07-15 21:48               ` Tom de Vries
2020-07-14 11:47 ` Tom de Vries

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=83v9vzyih8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=Alan.Hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).