From: David Woodhouse <dwmw2@infradead.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, Andy Whitcroft <apw@shadowen.org>
Subject: Re: [BUILD-FAILURE] linux-next: Tree for June 4 - firmware/keyspan/mpr.fw.gen.S
Date: Wed, 04 Jun 2008 18:52:10 +0100 [thread overview]
Message-ID: <1212601930.32207.134.camel@pmac.infradead.org> (raw)
In-Reply-To: <54a3f4cc48b03f9fe63be0bcd7c2ab20@kernel.crashing.org>
On Wed, 2008-06-04 at 19:19 +0200, Segher Boessenkool wrote:
> It is a new feature in GNU make 3.81, which was released slightly
> over two years ago.
Hm, Ok. I'll stick in a workaround. Thanks.
diff --git a/firmware/Makefile b/firmware/Makefile
index b4f758a..166a9b0 100644
--- a/firmware/Makefile
+++ b/firmware/Makefile
@@ -83,6 +83,13 @@ wordsize_deps := $(wildcard include/config/64bit.h include/config/32bit.h \
include/config/superh32.h include/config/superh64.h \
include/config/x86_32.h include/config/x86_64.h)
+# Workaround for ancient versions of make, where .SECONDEXPANSION doesn't work.
+# It'll end up depending on these targets, so make them a PHONY rule which
+# depends on _all_ the directories in $(firmware-dirs), and it'll work out OK.
+PHONY += $(objtree)/$$(%) $(objtree)/$(obj)/$$(%)
+$(objtree)/$$(%) $(objtree)/$(obj)/$$(%): $(firmware-dirs)
+ @true
+
# For the $$(dir %) trick, where we need % to be expanded first.
.SECONDEXPANSION:
--
dwmw2
next prev parent reply other threads:[~2008-06-04 17:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 8:00 linux-next: Tree for June 4 Stephen Rothwell
2008-06-04 11:46 ` [BUILD-FAILURE] linux-next: Tree for June 4 - firmware/keyspan/mpr.fw.gen.S Kamalesh Babulal
2008-06-04 11:50 ` David Woodhouse
2008-06-04 11:57 ` David Woodhouse
2008-06-04 17:19 ` Segher Boessenkool
2008-06-04 17:52 ` David Woodhouse [this message]
2008-06-04 18:20 ` Adrian Bunk
2008-06-04 21:33 ` David Woodhouse
2008-06-04 21:37 ` Adrian Bunk
2008-06-05 9:43 ` Kamalesh Babulal
2008-06-04 13:38 ` David Woodhouse
2008-06-05 9:13 ` Sam Ravnborg
2008-06-05 9:15 ` David Woodhouse
2008-06-05 10:44 ` Sam Ravnborg
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=1212601930.32207.134.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=apw@shadowen.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=segher@kernel.crashing.org \
--cc=sfr@canb.auug.org.au \
/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 NNTP newsgroup(s).