> 4) make menuconfig is further broken: on the initial run it does not set
> CONFIG_PCI even though config.in sets it for my model of alpha (LX164!).
> This caused headache until I used just plain "make config" which appeared
> to get things perfect.
Damn, this will be harder to fix than I thought. In fact it is still
broken in 2.1.88. :-(
The first problem is that arch/alpha/config.in uses define_bool to
set CONFIG_PCI, and there's a simple bug in Menuconfig's definition
of define_bool (it needs to actually define the value). I fixed this
bug in 2.1.77.
The second problem is a scripting problem in arch/alpha/config.in.
It unconditionally unsets CONFIG_PCI at the top of its scripts, and then
calls define_bool on CONFIG_PCI inside the "General Setup" menu.
Menuconfig executes statements inside a menu when the user enters the
menu. So even if the user goes into "General Setup" and comes back out,
Menuconfig re-builds the root menu by re-executing the statements in
arch/alpha/config.in, which blithely unset CONFIG_PCI.
In other words: it's wrong to clear variables in one menu and set them
in a sub-menu, because Menuconfig executes the statements in a menu
whenever that menu is entered or re-entered.
I have to shelve this bug but I'll get back to it when I get more time.
Regards,
Michael Chastain
<mailto:mec@shout.net>
"love without fear"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu