From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 21 Nov 2002 07:50:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 21 Nov 2002 07:50:58 -0500 Received: from smtpzilla5.xs4all.nl ([194.109.127.141]:57871 "EHLO smtpzilla5.xs4all.nl") by vger.kernel.org with ESMTP id ; Thu, 21 Nov 2002 07:50:58 -0500 Date: Thu, 21 Nov 2002 13:57:30 +0100 (CET) From: Roman Zippel X-X-Sender: roman@serv To: Adrian Bunk cc: linux-kernel@vger.kernel.org Subject: Re: 2.5 kconfig doesn't handle "&& m" correctly In-Reply-To: <20021121083912.GE11952@fs.tum.de> Message-ID: References: <20021121083912.GE11952@fs.tum.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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