linux-kernel - Re: -tip build failure: No rule to make target `/etc/sound/dsp001.ld'

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]

Date:	Fri, 27 Jun 2008 21:59:50 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Adrian Bunk" <bunk@...nel.org>
Cc:	"Ingo Molnar" <mingo@...e.hu>, "Sam Ravnborg" <sam@...nborg.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: -tip build failure: No rule to make target `/etc/sound/dsp001.ld'

On Fri, Jun 27, 2008 at 9:40 PM, Adrian Bunk <bunk@...nel.org> wrote:
> On Fri, Jun 27, 2008 at 09:25:05PM +0200, Vegard Nossum wrote:
>> Hi,
>>
>> I was just building a randconfig in tip/master and hit this:
>>
>> make[2]: *** No rule to make target `/etc/sound/dsp001.ld', needed by
>> `sound/oss/pss_boot.h'.  Stop.
>>
>> It seems to be done like this on purpose, but it breaks randconfig
>> builds. Is this something that should be using firmware API?
>>
>> I'm attaching the config. Please forward this in the right direction,
>> if such a thing exists.
>
> It's your fault - compile errors with CONFIG_STANDALONE=n are expected.

Ah, I see. In that case, shouldn't 'make randconfig' also make sure
that this option is always =n? Or do I have to do

make randconfig
make CONFIG_STANDALONE=n

? Are there any other options which have similar effects (build-time
dependencies on the environment) and need to be overridden? Or maybe
we could have 'make randconfig' output a helpful explanation in case
this option gets set?

Thanks for helping out.

(Who said that kernel development was easy? ;-))


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
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/