2.5 kconfig doesn't handle "&& m" correctly

From: Adrian Bunk (bunk@fs.tum.de)
Date: Thu Nov 21 2002 - 03:39:12 EST

Hi Roman,

while looking for the reason for a compile error in 2.5.48 I noticed the
following that seems to be a bug in the new kconfig:

The following is with a .config that was generated using
"make oldconfig":

<-- snip -->

$ grep SOUND_WAVEFRONT .config
CONFIG_SOUND_WAVEFRONT=y
$

<-- snip -->

sound/oss/Kconfig contains the following:

<-- snip -->

...
config SOUND_WAVEFRONT
        tristate "Full support for Turtle Beach WaveFront (Tropez Plus, Tropez, Maui) synth/soundcards"
        depends on SOUND_OSS && m
...

<-- snip -->

It seems the "&& m" (a common way to ensure that something can only be
built modular) isn't handled correctly.

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

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

This archive was generated by hypermail 2b29 : Sat Nov 23 2002 - 22:00:35 EST