From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Alan Hayward <Alan.Hayward@arm.com>
Subject: Re: [PATCH] Require GNU make 3.82
Date: Tue, 16 Jul 2019 00:51:00 -0000 [thread overview]
Message-ID: <20190715175153.4effe7e8@f29-4.lan> (raw)
In-Reply-To: <20190715101124.77677-1-alan.hayward@arm.com>
On Mon, 15 Jul 2019 10:11:29 +0000
Alan Hayward <Alan.Hayward@arm.com> wrote:
> Gdbserver has failed to build with GNU make 3.81 since commit 08f10e02be.
>
> Update the NEWS file to state that versions earlier than 3.82 are not
> supported.
>
> 3.82 was released in 2010, 3.81 was released 2006. A quick investigation
> of the default GNU make version provided across various distros found the
> earliest provided version to be 3.82:
> *RHEL 7, Centos 6 - make 3.82
> *Fedora 27 - make 4.2.1
> *OpenSuse 42.2, SLES11 - make 4.2.1
> *Ubuntu 16.04/18.04 - make 4.1
> *Debian Jessie - make 4.0
>
> Note that Glibc requires at least 4.0, whereas GCC still allows 3.81.
>
> gdb/ChangeLog:
>
> 2019-07-15 Alan Hayward <alan.hayward@arm.com>
>
> * NEWS: Require GNU make 3.82.
This seems okay to me, though I think that Eli needs to approve it.
Regardless, I think you should wait a few days to push it in case
there are any objections. (The other solution is to rewrite the
Makefile rules that caused the breakage.)
Kevin
next prev parent reply other threads:[~2019-07-16 0:51 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 [this message]
2019-07-16 10:36 ` Alan Hayward
2019-07-18 6:17 ` Eli Zaretskii
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=20190715175153.4effe7e8@f29-4.lan \
--to=kevinb@redhat.com \
--cc=Alan.Hayward@arm.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