Hi,
On Thu, 21 Feb 2002, Giacomo Catenazzi wrote:
> 1) default: Eric proposed to include defaults in configuration,
> but it seems that is a bad things, and defaults should be arch
> specific. (I don't remember the discussion, but you can
> parse the kbuild list, torque.net time)
The defaults are just 1:1 representation of the current define_xxx
statements. These can be of course later moved or depreciated or whatever.
> 2) One of the problem in actual configure are the dependencies.
> FOO depend on BAR and BEER.
> Wat are the possible value of FOO if BAR=m, BEER=y.
> In kernel we have some drivers thet need foo to be n or y,
> in other cases: n or m.
> The logical operators hide the true dependency table.
> (don't expect developers read the docs: the logical operators
> seems like C operators, so they use like C, but they forget
> the third case (=m) ).
For most cases I've seen it can be very simply defined with:
(a && b && ...) = min(a, b, ...)
(a || b || ...) = max(a, b, ...)
for 'n'=0, 'm'=1, 'y'=2
I have to check the other cases and I haven't look too closely, yet, but
e.g. in this case it goes wrong:
config: FB_MATROX_G450
dep_tristate
prompt: G450/G550 second head support
dep: (VT? && EXPERIMENTAL? && FB? && EXPERIMENTAL? && PCI? && FB_MATROX??!=n && FB_MATROX_G100?)
CONFIG_FB_MATROX_G450 can be defined to 'y' and CONFIG_FB_MATROX to 'm',
the result is that the build goes wrong. By removing '!=n' above rule
would produce the correct result.
Do you have some real examples?
> Do you use the python identation mode?
No python. Just c, flex and bison. :-)
bye, Roman
-
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 : Sat Feb 23 2002 - 21:00:32 EST