Re: RFC: kconfig select warnings bogus?

Russell King
2007-05-20T09:43:49Z

On Sun, May 20, 2007 at 02:02:35AM +0200, Adrian Bunk wrote:
> On Sat, May 19, 2007 at 04:22:39PM -0700, Andrew Morton wrote:
> > On Sun, 20 May 2007 01:05:37 +0200 Adrian Bunk <bunk@stusta.de> wrote:
> >
> > > Look for example at the last one in drivers/input/mouse/Kconfig:
> > >
> > > config MOUSE_ATARI
> > > tristate "Atari mouse"
> > > depends on ATARI
> > > select ATARI_KBD_CORE
> > >
> > > This is perfectly correct (the select'ed symbol is only unavailable when
> > > the dependency can't be fulfilled), and all things to "fix" the warning
> > > will make it worse.
> >
> > If ATARI is unset then we shouldn't be generating the "'select' used by
> > config symbol 'KEYBOARD_ATARI' refers to undefined symbol 'ATARI_KBD_CORE'"
> > warnings, should we?
>
> Exactly.

If we do that we need to try a million and one Kconfig option combinations
to find undefined symbols. Not practical.

(And no, allyconfig really doesn't hack it on non-x86 platforms, no matter
how much people whinge that it should do. It's a pipedream to make it so.)

--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/