mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Andrew Benton <b3nton@gmail.com>,
	linux-kbuild <linux-kbuild@vger.kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: make-3.82 and built in firmware
Date: Fri, 6 Aug 2010 15:46:24 +0200	[thread overview]
Message-ID: <20100806134624.GA25864@merkur.ravnborg.org> (raw)
In-Reply-To: <4C5C03D5.1040108@gmail.com>

On Fri, Aug 06, 2010 at 01:45:09PM +0100, Andrew Benton wrote:
> Hello World
> I recently upgraded to the latest version of make, 3.82. One of the 
> problems I've had with it is that I can no longer recompile my kernel 
> with built in firmware enabled. If I have 
> CONFIG_FIRMWARE_IN_KERNEL=y
> then the build fails like so:
> 
>   IKCFG   kernel/config_data.h
>   CC      kernel/configs.o
>   LD      kernel/built-in.o
> make[2]: *** No rule to make target `/tmp/linux-build-dir/firmware/radeon/', needed by `firmware/radeon/R100_cp.bin.gen.S'.  Stop.
> make[1]: *** [firmware] Error 2
> make: *** [sub-make] Error 2
> andy:~/save/src/linux-2.6$ 

Thanks for the report.
I saw a similar report whare make 3.82 was accused - maybe this was also from you.

Can you positively confirm that this is a make 3.82 issue - or do you just expect so?

To narrow down this a bit further can I ask you
to send the output of "make -j1 V=1" - especially
the lines before you see the bug.

[-j1 is to force you to avoid parallel makes
 as this may clutter up the output]

Please also post a copy of your configuration
as this allows us to better reproduce what you see.

> Please CC, I'm not subscribed
No problem - we always do so at lkml.

	Sam

  reply	other threads:[~2010-08-06 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-06 12:45 Andrew Benton
2010-08-06 13:46 ` Sam Ravnborg [this message]
2010-08-06 14:06   ` Andrew Benton

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=20100806134624.GA25864@merkur.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=b3nton@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®