On Mon, 22 Jul 2002, Russell King wrote:
> On Mon, Jul 22, 2002 at 11:08:41AM +1000, Keith Owens wrote:
> > It is required if you ever want autoconfigure to work, that
> > distinguishes between "" (undefined) and "n" (explicitly turned off).
> > Forward planning.
>
> Wouldn't it be better to fix the existing config tools to output "=n"
> instead of "# CONFIG_foo is not set" ? IIRC they do the translation
> back and forth internally anyway, so it should be just a matter of
> removing some code from the tools.
The point is, what would such a change buy us? It needs going through all
Makefiles, updating
ifdef CONFIG_XYZ
to
ifneq ($(CONFIG_XYZ),n)
(or ifeq ($(CONFIG_XYZ),y) when we now it's a bool)
Actually, now this won't handle the CONFIG_XYZ unset case, which may well
happen since a part of Config.in which would set or unset the symbols
may not even get sourced.
So we really have to use
ifneq ($(subst n,,$(CONFIG_XYZ),)
instead. That's ugly and doesn't have any advantage over what we have
now, AFAICS.
Inside the Config.in scripts it's annoying that you have to check against
"n" || "" (or ! ("y" || "m") ). The reasons for that lie, for all I can
tell, in the use of sh/bash for the original Configure script. In any
case, if this behavior is considered too annoying, it should be fixed in
the config system, but there's no reason to change the Makefile/.config
syntax, too.
(I think it may actually possible to fix it even within Configure, by just
always using <undef> instead of "n" - Configure needs to keep track of all
the encountered symbols anyway - but I didn't try. This would also
decrease the confusion, as then both the Makefiles and Config.in would
both use "y","m",<undef>.
W.r.t autoconfigure, I think that can easily be achieved using/extending
the existing .config format.
Just have
# CONFIG_FOO is not set
vs
# CONFIG_FOO=n
or even
<CONFIG_FOO not mentioned in .config>
vs the current
# CONFIG_FOO is not set
Should be nicely compatible with all existing tools.
--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/
This archive was generated by hypermail 2b29 : Tue Jul 23 2002 - 22:00:38 EST