Messages in this thread | | | Date | Fri, 27 Jun 2008 22:04:14 +0200 | From | Sam Ravnborg <> | Subject | Re: -tip build failure: No rule to make target `/etc/sound/dsp001.ld' |
| |
On Fri, Jun 27, 2008 at 09:59:50PM +0200, Vegard Nossum wrote: > On Fri, Jun 27, 2008 at 9:40 PM, Adrian Bunk <bunk@kernel.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
Create a file fixed.config with the config options that may not change and use:
make KCONFIG_ALLCONFIG=fixed.config randconfig
STANDALONE is one of them - I recall Ingo has a well tested set of options he always forces to specific values.
[I may have the syntax wrong for KCONFGI_ALLCONFIG - please see README].
Sam
| |