[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 Thu, 2006-11-16 at 20:07 -0800, Randy Dunlap wrote:
> Hi,
> I have a (randconfig) build of 2.6.19-rc5-mm2 with:
> which selects DEBUG_FS, so DEBUG_FS=y, but DEBUG_FS depends on
> SYSFS, and SYSFS is not set in the randconfig.
> This randconfig causes this build error:
> fs/built-in.o: In function `debugfs_init':
> inode.c:(.init.text+0xdb2): undefined reference to `kernel_subsys'
> 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
> .config is at

Actually, no, I don't think this is the right thing to do. If we can't
persuade selected CONFIG options to give an inherited dependency to the
selectee, then the only other option is to make sure that selectable
config options have no dependencies (i.e. they select everything they


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 23:13    [W:0.076 / U:0.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site