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.
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
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.
config STANDALONE
bool "Select only drivers that don't need compile-time external firmware" if EXPERIMENTAL
default y
help
Select this option if you don't have magic firmware for drivers that
need it.
If unsure, say Y.
And you have this set to 'n' so it is expected.
Sam
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.
> Vegard
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
On Fri, Jun 27, 2008 at 9:40 PM, Adrian Bunk <[email protected]> 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
On Fri, Jun 27, 2008 at 09:59:50PM +0200, Vegard Nossum wrote:
> On Fri, Jun 27, 2008 at 9:40 PM, Adrian Bunk <[email protected]> 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
On Fri, Jun 27, 2008 at 09:59:50PM +0200, Vegard Nossum wrote:
> On Fri, Jun 27, 2008 at 9:40 PM, Adrian Bunk <[email protected]> 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
>...
KCONFIG_ALLCONFIG can be used for this.
> Vegard
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed