> [Andi Kleen]
> > I don't see why it is unmaintainable. What is so bad with these ifs?
> > 64bit cleanness is just another dependency, nothing magic and fundamentally
> > hard.
> [...]
> > (unfortunately there is no dep_tristate ... !$CONFIG_64BIT)
> > Alternatively CONFIG_NO_64BIT to work around this issue.
>
> The real solution (imo) is to add !$CONFIG_FOO support to the config
> language. Fortunately this is quite easy. What do you people think?
> I didn't do xconfig or config-language.txt but I can if desired.
As you're hacking Configure anyway, what about "fixing"
dep_tristate ' ..' CONFIG_FOO $CONFIG_BAR,
which doesn't work as expected when CONFIG_BAR is not set (as opposed to
"n"), to consider an unset CONFIG_BAR equivalent to "n" in this case?
(The rather hacky way I'd imagine to do so is to look at all used
$CONFIG_* in a Config.in file before sourcing it and setting them to "n")
--Kai
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/