From: Andrew Benton <b3nton@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: make-3.82 and built in firmware
Date: Fri, 06 Aug 2010 15:06:03 +0100 [thread overview]
Message-ID: <4C5C16CB.5060705@gmail.com> (raw)
In-Reply-To: <20100806134624.GA25864@merkur.ravnborg.org>
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
On 06/08/10 14:46, Sam Ravnborg wrote:
> 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?
>
I'm certain that it relates to make-3.82. I've installed make-3.81 just so I can recompile my kernel. If I use:
make-3.81 O=/tmp/linux-build-dir -j4
then the build succeeds.
> 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.
make -j1 V=1 O=/tmp/linux-build-dir
... snip ...
LD sound/usb/caiaq/built-in.o
LD sound/usb/misc/built-in.o
LD sound/usb/usx2y/built-in.o
LD sound/usb/built-in.o
CC sound/last.o
LD sound/built-in.o
MK_FW firmware/rt2561s.bin.gen.S
AS firmware/rt2561s.bin.gen.o
make[2]: *** No rule to make target `/tmp/linux-build-dir/firmware/radeon/', needed by `firmware/radeon/R700_rlc.bin.gen.S'. Stop.
make[1]: *** [firmware] Error 2
make: *** [sub-make] Error 2
andy:~$
> Please also post a copy of your configuration
> as this allows us to better reproduce what you see.
>
I've attached /proc/config.gz
Andy
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 13199 bytes --]
prev parent reply other threads:[~2010-08-06 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 12:45 make-3.82 and built in firmware Andrew Benton
2010-08-06 13:46 ` Sam Ravnborg
2010-08-06 14:06 ` Andrew Benton [this message]
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=4C5C16CB.5060705@gmail.com \
--to=b3nton@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.