From: Sam Ravnborg <sam@ravnborg.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@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: Thu, 5 Jun 2008 11:13:19 +0200 [thread overview]
Message-ID: <20080605091319.GA17469@uranus.ravnborg.org> (raw)
In-Reply-To: <1212586717.32207.71.camel@pmac.infradead.org>
On Wed, Jun 04, 2008 at 02:38:37PM +0100, David Woodhouse wrote:
> On Wed, 2008-06-04 at 17:16 +0530, Kamalesh Babulal wrote:
> > Hi Stephen,
> >
> > The next-20080604 kernel build fails on the x86_64 machine
> >
> > make[1]: *** No rule to make target `/usr/local/autobench/autotest/tmp/build/linux/$(dir)', needed by `firmware/keyspan/mpr.fw.gen.S'. Stop.
> > make: *** [firmware] Error 2
>
> Does this 'fix' it?
The correct fix is to get rid of make 3.81 features.
We do want the kernel buildable with make 3.79 and we have today only two
places where we do need a newer version of make:
scripts/Makefile.headerinst
and now
firmware/Makefile
Both places should be reworked to avoid this dependency.
I plan to take care of Makfile.headerinst soonish in an attempt
to speed up the checking process (has been on my TODO list for a long time),
And we should not introuduce the below make 3.81 specific feature.
I have not looked into alternative - sorry.
Sam
next prev parent reply other threads:[~2008-06-05 9:12 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
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 [this message]
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=20080605091319.GA17469@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=apw@shadowen.org \
--cc=dwmw2@infradead.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).