From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Make 3.82 does behave differently than make 3.81 for sure, but ...
Date: Mon, 30 Aug 2010 22:00:21 +0200 [thread overview]
Message-ID: <8739tvyip6.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20100830163153.GA12776@merkur.ravnborg.org> (Sam Ravnborg's message of "Mon, 30 Aug 2010 18:31:53 +0200")
>>>>> "Sam" == Sam Ravnborg <sam@ravnborg.org> writes:
Hi,
Sam> make 3.81 accept the following:
Sam> foo foo%: bar
Sam> command
Sam> With make 3.82 you need to split this up as:
Sam> foo: bar
Sam> command
Sam> foo%: bar
Sam> command
Yeah, saw the kernel changes passing by. I haven't had time to test
building with make 3.82 yet though (it's not in Debian yet), so we might
have something similar lingering around somewhere ..
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-08-30 20:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 11:45 [Buildroot] package/atk/atk.mk:43: *** recipe commences before first target. Stop James J. Dines
2010-08-30 13:05 ` Yann E. MORIN
2010-08-30 13:37 ` Peter Korsgaard
2010-08-30 14:46 ` James J. Dines
2010-08-30 15:01 ` Yann E. MORIN
2010-08-30 15:44 ` [Buildroot] Make 3.82 does behave differently than make 3.81 for sure, but James J. Dines
2010-08-30 16:31 ` Sam Ravnborg
[not found] ` <4C7BE3C4.1060706@jdines.net>
[not found] ` <20100830185017.GA12921@merkur.ravnborg.org>
2010-08-30 19:01 ` [Buildroot] Make 3.82 does behave differently than make 3.81 James J. Dines
2010-08-30 20:00 ` Peter Korsgaard [this message]
2010-08-30 20:21 ` [Buildroot] Make 3.82 does behave differently than make 3.81 for sure, but James J. Dines
2010-08-30 20:57 ` Peter Korsgaard
2010-08-30 21:10 ` James J. Dines
2010-08-30 21:36 ` Peter Korsgaard
2010-08-30 23:28 ` James J. Dines
2010-08-31 22:17 ` [Buildroot] Make 3.82 testing progress update James J. Dines
2010-08-30 22:15 ` [Buildroot] Make 3.82 does behave differently than make 3.81 for sure, but Malte Starostik
2010-08-31 12:38 ` James J. Dines
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=8739tvyip6.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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