From: Roland McGrath <roland@redhat.com>
To: Andreas Schwab <schwab@redhat.com>
Cc: libc-hacker@sourceware.org
Subject: Re: [PATCH] Work around shortest-stem feature in make 3.82+
Date: Fri, 10 Sep 2010 10:34:00 -0000 [thread overview]
Message-ID: <20100910103412.41A8E405D5@magilla.sf.frob.com> (raw)
In-Reply-To: Andreas Schwab's message of Friday, 10 September 2010 12:15:35 +0200 <m3tylxrjjs.fsf@hase.home>
> make 3.82+ no longer selects pattern rules by order, but by shortest
> stem, so we need to add more rules to make sure we still get the right
> matches.
Sweet mother of god, what is that guy thinking? I shudder to think at all
the subtle breakage introduced to makefile magic that has worked the same
for 20 years now. He's kind of making me regret choosing him as maintainer.
Even I have a hard time figuring out what exactly this dismal change could
mean for complex uses of pattern rules like we have.
next prev parent reply other threads:[~2010-09-10 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 10:15 Andreas Schwab
2010-09-10 10:34 ` Roland McGrath [this message]
2010-09-10 11:11 ` Andreas Schwab
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=20100910103412.41A8E405D5@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=libc-hacker@sourceware.org \
--cc=schwab@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).