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

From: Roman Zippel (zippel@linux-m68k.org)
Date: Thu Nov 21 2002 - 07:57:30 EST


Hi,

On Thu, 21 Nov 2002, Adrian Bunk wrote:

> 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.

Did you disable modules? When modules are disabled tristate symbols are
treated like booleans, that means they are visible if the dependencies are
different than 'n'. For this it should be possible to automatically add
'&& MODULES' if the parser sees a 'm'. I'll have to check this out.

bye, Roman

-
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:36 EST