[lkml]   [2001]   [Jun]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.4.6p6: numerous dep_{bool,tristate} $CONFIG_ARCH_xxx bugs
Hi Russell, Adam.

>> So, I guess something like Keith Owens's patch would be the way
>> to go, with some additional definitions (CONFIG_AGP, CONFIG_PCI,
>> CONFIG_ISA, CONFIG_EISA, CONFIG_PCMCIA, and possibly others).
>> I am not sure which other conditionals might also be incorrectly
>> ignored by some instances of dep_xxx. Below, I have included a
>> list of the 52 CONFIG_* variables that are used as arguments to
>> dep_xxx in 2.4.6-pre6 and appear in arch/*/

> I have confirmed that Keith Owens patch doesn't work with
> xconfig - you can't select any option which has been
> define_bool'd to 'n'.

I've followed this thread with interest, and think I've followed both
sides of the argument, so can I summarise:

1. Adam's point is that there are dep_* statements in the config
setup that have been used to say that a particular option is
dependant upon a particular architecture, but this doesn't work.

2. Russell's point is that Adam's point is correct, but the patch
that Adam submitted can't be used as it breaks other things.

3. MY understanding of the situation is that ALL architecture
specific config lines are EXPECTED to be in the arch/*/
files, where they will only even be seen when the relevant
architecture is being compiled for.

As a result of this, I would summarise this discussion as saying that
there is a bug in the kernel config scripts in that some options that
should be located in the architecture-specific config files are in the
all-architecture config files instead.

Best wishes from Riley.

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: 2005-03-22 12:55    [W:0.045 / U:0.560 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site