Re: architectures with their own "config PCMCIA"

[Sam Ravnborg <sam@ravnborg.org>]

On Wed, Aug 11, 2004 at 10:17:25PM +0200, Adrian Bunk wrote:
> On Sat, Aug 07, 2004 at 08:12:56PM +0200, Arnd Bergmann wrote:
> >...
> > On Samstag, 7. August 2004 19:25, Adrian Bunk wrote:
> > > Is there eny reason for such options that are never visible nor enabled,  
> > > or could they be removed?
> > 
> > Yes, the reason is that some other options depend on them. We added the
> > PCMCIA option to arch/s390/Kconfig to stop kbuild from asking about
> > some drivers that won't work anyway.
> > 
> > E.g. drivers/scsi/pcmcia starts with
> > 
> > menu "PCMCIA SCSI adapter support"
> > 	depends on SCSI!=n && PCMCIA!=n && MODULES
> > 
> > which evaluate to true if the PCMCIA option is not known. Changing
> > that to
> > 
> > menu "PCMCIA SCSI adapter support"
> > 	depends on SCSI && PCMCIA && MODULES
> > 
> > solves this in a different way, but I'm not 100% sure if it still has
> > the same meaning.
> 
> Roman, is it intentional that PCMCIA!=n is true if there's no PCMCIA 
> option, or is it simply a bug?

Roman, a related Q.
Why not error out, or at least warn when encountering an unknow
symbol in a 'depends on' statement?

I took a quick look, but did not initially see how to actually implemnt it.
Considering something in the bottom of menu_finalize()?

	Sam