From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH 3/4] Makefile: Replace old suffix rules with pattern rules
Date: Wed, 16 Nov 2016 19:11:00 -0000 [thread overview]
Message-ID: <773f613d-7157-258e-bb1c-daf86a7ec0d3@redhat.com> (raw)
In-Reply-To: <20161116160808.12830-4-simon.marchi@ericsson.com>
On 11/16/2016 04:08 PM, Simon Marchi wrote:
> From: Simon Marchi <simon.marchi@polymtl.ca>
>
> As mentioned here [1], suffix rules are obsolete and have been
> superseeded with pattern rules. People (myself included, before writing
> this patch) are more likely to know what pattern rules are than suffix
> rules.
>
> AFAIK, .SUFFIXES targets are only used for those rules, and can be
> removed as well.
>
> New in v2:
>
> - Replace rule in gdbserver/Makefile.in as well.
>
> [1] https://www.gnu.org/software/make/manual/html_node/Suffix-Rules.html
>
> gdb/ChangeLog:
>
> * Makefile.in (.c.o): Replace rule with ...
> (%.o: %.c): ... this one.
> (.po.gmo): Replace rule with ...
> (%.gmo: %.po): ... this one.
> (.po.pox): Replace rule with ...
> (%.pox: %.po): ... this one.
> (.y.c): Replace rule with ...
> (%.c: %.y): ... this one.
> (.l.c): Replace rule with ...
> (%.c: %.l): ... this one.
> (.SUFFIXES): Remove all instances.
>
> gdb/gdbserver/ChangeLog:
>
> * Makefile.in (.c.o): Replace rule with ...
> (%.o: %.c): ... this one.
IMO, whether to explicitly remove default suffixes from the
the implicit rule suffixes list for efficiency is a separate
subject, since we're not currently doing it either.
Just to be sure none of the default suffix rules is necessary,
can you confirm:
1. that "make -r" (from scratch) still works.
2. that "make -r diststuff" in the gdb build dir still works.
If the above work, then this is OK with me to push in.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-11-16 19:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 16:11 [PATCH 0/4] Require GNU make 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 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 [this message]
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 ` Simon Marchi
2016-11-16 17:12 ` Pedro Alves
2016-11-16 17:09 ` 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=773f613d-7157-258e-bb1c-daf86a7ec0d3@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
--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