linux-kernel - Re: make-3.82 and built in firmware

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100806134624.GA25864@merkur.ravnborg.org>
Date:	Fri, 6 Aug 2010 15:46:24 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Andrew Benton <b3nton@...il.com>,
	linux-kbuild <linux-kbuild@...r.kernel.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: make-3.82 and built in firmware

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/