From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] Document new hard requirement on GNU make
Date: Thu, 17 Nov 2016 12:39:00 -0000 [thread overview]
Message-ID: <98fd2002-3c4a-504d-2dab-e1590005b6e0@redhat.com> (raw)
In-Reply-To: <ee1f94f5-91d6-6a26-d0c9-13ed47852cce@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2705 bytes --]
On 11/16/2016 11:34 PM, Pedro Alves wrote:
> On 11/16/2016 10:04 PM, Simon Marchi wrote:
>> On 2016-11-16 12:23, Eli Zaretskii wrote:
>>>> With make >= 3.82, it would do the right thing (choose the second one),
>>>> by choosing the rule with the shorter stem. Before that, it used the
>>>> order of definition (the first that matches wins). So it would be nice
>>>> for that reason to require >= 3.82, but it's also possible to work
>>>> around if that's too recent.
>>>
>>> 3.82 shouldn't be a problem, I think.
>>
>> Oops, I said that without even checking the version I have on my system.
>> Ubuntu 14.04, strangely, has make 3.81. Apparently that was because of
>> a critical bug on Debian with 3.82, which stayed open for a long time,
>> preventing the upgrade. Debian and its derivatives, including Ubuntu,
>> were stuck with that for a long time.
>>
>> Refs:
>> http://stackoverflow.com/questions/31912233/how-to-update-make-3-81-linux
>> https://lwn.net/Articles/569920/
>>
>> I don't think it's worth complicating the lives of those users just to
>> get the benefit of the behaviour change I mentioned.
>>
>> So I'm back at having no idea what version we should require.
>
> I think we should go with the same requirement as gcc (3.80), as
> seen on the top level Makefile.in:
>
> @if gcc
> ifeq (,$(.VARIABLES)) # The variable .VARIABLES, new with 3.80, is never
> empty.
> $(error GNU make version 3.80 or newer is required.)
> endif
> @endif gcc
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
[-- Attachment #2: check-make-ver --]
[-- Type: text/plain, Size: 2064 bytes --]
#!/bin/bash
rm -f make-ver.gcc*.fsffrance.org
function kill_ssh() {
ps | grep ssh | awk '{print $1}' | xargs kill
}
function ctrl_c() {
kill_ssh
}
trap ctrl_c INT
function do_ssh() {
cmd="sh -c '[ -f /etc/os-release ] && cat /etc/os-release; printf \"hostname: \"; hostname; printf \"uname: \"; uname -a; ((make -v 2>&1 | grep -q GNU) && make -v) || ((gmake -v 2>&1 | grep -q GNU) && gmake -v)' 2>&1"
# Retry 5 times, wait 5 seconds between attempts.
for i in {1..5}
do
ssh -q -o UserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -oBatchMode=yes gcc$h.fsffrance.org "$cmd" >make-ver.gcc$h.fsffrance.org 2>&1 && break || sleep 5;
done
}
for h in `seq 1 250`
do
do_ssh &
done
echo "waiting 30s..."
sleep 30
kill_ssh
# Move inaccessible hosts out of the way.
mkdir -p nohost
find . -maxdepth 1 -size 0 | while read line; do mv $line nohost/; done
grep -l "Network is unreachable" make-ver.gcc* | while read line; do mv $line nohost/; done
grep -l "Connection timed out" make-ver.gcc* | while read line; do mv $line nohost/; done
grep -l "Permission denied" make-ver.gcc* | while read line; do mv $line nohost/; done
grep -l "Could not resolve hostname" make-ver.gcc* | while read line; do mv $line nohost/; done
grep -l "Connection refused" make-ver.gcc* | while read line; do mv $line nohost/; done
printf "Number of accessible hostnames: "
ls make-ver.gcc* | wc -l
printf "Number of inaccessible hostnames: "
ls nohost/make-ver.gcc* | wc -l
printf "Hostnames with GNU Make: "
grep -l "GNU Make" make-ver.gcc* | wc -l
printf "Hostnames without GNU Make: "
grep -L "GNU Make" make-ver.gcc* | wc -l
echo "Distribution: "
grep -h "GNU Make" make-ver.gcc* | sort | uniq -c
# Kill dups (found via uname in the ssh command)
(fdupes -f . | grep -v '^$' | xargs rm -v)2>&1 >/dev/null
printf "Unique hosts with GNU Make: "
grep -l "GNU Make" make-ver.gcc* | wc -l
printf "Unique hosts without GNU Make: "
grep -L "GNU Make" make-ver.gcc* | wc -l
echo "Distribution: "
grep -h "GNU Make" make-ver.gcc* | sort | uniq -c
next prev parent reply other threads:[~2016-11-17 12: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 3/4] Makefile: Replace old suffix " 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-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 ` Pedro Alves
2016-11-16 17:12 ` Simon Marchi
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 [this message]
2016-11-17 13:39 ` Simon Marchi
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-17 17:05 ` [PATCH 0/4] Require " 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=98fd2002-3c4a-504d-2dab-e1590005b6e0@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).