From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <palves@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] Document new hard requirement on GNU make
Date: Thu, 17 Nov 2016 13:39:00 -0000 [thread overview]
Message-ID: <1c2e0192d07bb7ac2a1ed277f8d9934c@polymtl.ca> (raw)
In-Reply-To: <98fd2002-3c4a-504d-2dab-e1590005b6e0@redhat.com>
On 2016-11-17 07:39, Pedro Alves wrote:
> Actually, I take that back. I was just using "makes it easier
> to have a single top level check", but that's not really a good
> rationale. I wouldn't want to be stuck if gcc decides to
> move at a glacial pace.
>
> Probably a policy similar to the C++NN one makes more sense.
>
> I see now that 3.81 was released in 2006, so should not be
> a problem to require it.
>
> OOC, I wrote a quick&dirty script (attached) to check for GNU Make
> availability in the GCC compile farm. It tries all gcc*.fsffrance.org
> from 1 to 250. I don't have access to all machines setup, as some are
> multiplexed on a single IP with different ports, requiring tweaking
> the local ssh config. However, what I found was already interesting,
> I believe. Here's the result:
>
> Number of accessible hostnames: 66
> Number of inaccessible hostnames: 184
> Hostnames with GNU Make: 66
> Hostnames without GNU Make: 0
> Distribution:
> 56 GNU Make 3.81
> 2 GNU Make 3.82
> 7 GNU Make 4.0
> 1 GNU Make 4.1
> Unique hosts with GNU Make: 20
> Unique hosts without GNU Make: 0
> Distribution:
> 10 GNU Make 3.81
> 2 GNU Make 3.82
> 7 GNU Make 4.0
> 1 GNU Make 4.1
>
> I.e., I didn't find a single machine still stuck with GNU Make 3.80.
>
> Thanks,
> Pedro Alves
Thanks for doing this! That, gives us some data on which to base
ourselves to require make 3.81.
Eli, I would update the NEWS entry to:
* Building GDB and GDBserver now requires GNU make >= 3.81.
It is no longer supported to build GDB or GDBserver with another
implementation of the make program or en earlier GNU make version.
Does it look good to you?
Where else should that dependency be documented?
next prev parent reply other threads:[~2016-11-17 13:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 16:11 [PATCH 0/4] Require " Simon Marchi
2016-11-16 16:10 ` [PATCH 4/4] Makefile: Replace explicit subdir rules with pattern rules Simon Marchi
2016-11-16 17:11 ` Pedro Alves
2016-11-16 16:12 ` [PATCH 2/4] Remove code that checks for GNU/non-GNU make Simon Marchi
2016-11-16 16:32 ` Eli Zaretskii
2016-11-16 16:39 ` Andreas Schwab
2016-11-16 17:12 ` Simon Marchi
2016-11-16 17:12 ` Pedro Alves
2016-11-16 17:09 ` Pedro Alves
2016-11-16 16:12 ` [PATCH 1/4] Document new hard requirement on GNU make Simon Marchi
2016-11-16 16:29 ` Eli Zaretskii
2016-11-16 17:05 ` Simon Marchi
2016-11-16 17:23 ` Eli Zaretskii
2016-11-16 22:05 ` Simon Marchi
2016-11-16 23:34 ` Pedro Alves
2016-11-17 12:39 ` Pedro Alves
2016-11-17 13:39 ` Simon Marchi [this message]
2016-11-17 16:10 ` Eli Zaretskii
2016-11-17 3:35 ` Eli Zaretskii
2016-11-17 10:06 ` Jonas Maebe
2016-11-17 12:43 ` Pedro Alves
2016-11-16 16:12 ` [PATCH 3/4] Makefile: Replace old suffix rules with pattern rules Simon Marchi
2016-11-16 16:35 ` Eli Zaretskii
2016-11-16 16:56 ` Pedro Alves
2016-11-16 17:14 ` Eli Zaretskii
2016-11-16 17:32 ` Pedro Alves
2016-11-16 17:49 ` Eli Zaretskii
2016-11-16 17:58 ` Pedro Alves
2016-11-16 19:38 ` Simon Marchi
2016-11-16 19:58 ` Pedro Alves
2016-11-16 20:18 ` Simon Marchi
2016-11-16 19:11 ` Pedro Alves
2016-11-17 16:52 ` Simon Marchi
2016-11-17 16:57 ` Pedro Alves
2016-11-17 17:05 ` [PATCH 0/4] Require GNU make 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=1c2e0192d07bb7ac2a1ed277f8d9934c@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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