From: Simon Marchi <simon.marchi@polymtl.ca>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] Require GNU make
Date: Thu, 17 Nov 2016 17:05:00 -0000 [thread overview]
Message-ID: <a81a75201f5fa52ee1eda8ec80fc7bcd@polymtl.ca> (raw)
In-Reply-To: <20161116160808.12830-1-simon.marchi@ericsson.com>
On 2016-11-16 11:08, Simon Marchi wrote:
> Following the discussions in
>
> https://sourceware.org/ml/gdb-patches/2016-11/msg00326.html
>
> I am sending this patch series which makes GNU make mandatory for
> building GDB
> and GDBserver.
>
> - Patch 1 simply updates the NEWS file
> - Patch 2 removes code that is conditional on make being GNU make or
> not.
> - Patches 3 and 4 make use of pattern rules, a GNU make-specific
> feature.
>
> Patches 3 and 4 replace patches 1 and 2 in the original series.
>
> Simon Marchi (4):
> Document new hard requirement on GNU make
> Remove code that checks for GNU/non-GNU make
> Makefile: Replace old suffix rules with pattern rules
> Makefile: Replace explicit subdir rules with pattern rules
>
> gdb/Makefile.in | 835
> +++++----------------------------------------
> gdb/NEWS | 5 +
> gdb/configure | 97 ------
> gdb/configure.ac | 11 -
> gdb/gdbserver/Makefile.in | 36 +-
> gdb/gdbserver/configure | 97 ------
> gdb/gdbserver/configure.ac | 11 -
> gdb/testsuite/Makefile.in | 88 +++--
> gdb/testsuite/configure | 99 ------
> gdb/testsuite/configure.ac | 11 -
> 10 files changed, 141 insertions(+), 1149 deletions(-)
Thanks everybody for the reviews and comments, I have now pushed this
series.
I'll follow-up with:
- See if binutils can require GNU make as well, and perhaps have a
check in the top-level makefile
- Disable default implicit rules with .SUFFIXES.
Simon
prev parent reply other threads:[~2016-11-17 17:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 16:11 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
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 ` Simon Marchi [this message]
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=a81a75201f5fa52ee1eda8ec80fc7bcd@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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