[lkml]   [2006]   [Nov]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: how to handle indirect kconfig dependencies
On Fri, Nov 17, 2006 at 02:55:09PM +0100, Stefan Richter wrote:
> Randy Dunlap wrote:
> > I have a (randconfig) build of 2.6.19-rc5-mm2 with:
> [...]
> > so the question is:
> > (How) can kconfig follow the dependency chain and either
> > - prevent this odd config combination or
> > - see that 'select DEBUG_FS' implies 'select SYSFS' and then enable SYSFS
> > ?
> >
> > I don't believe that the right answer is to add
> > depends on SYSFS
> I know this doesn't concludingly answer your question, but: All of the
> various shipped tools to generate .config need to be fixed to recognize
> "select" to imply a dependency like "depends on" does.

"All of the various shipped tools ... need to be fixed" is a bit
misleading since one of the features of the 2.6 kconfig is that this
code is shared by all tools.

> Stefan Richter



"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
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-11-20 19:17    [W:0.099 / U:37.284 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site