Re: [KBUILD] How do we handle autoconfiguration?

From: Michael Elizabeth Chastain (
Date: Tue Dec 26 2000 - 19:52:15 EST

esr> # PROCESSOR is string valued; we capture stdout from the probe
esr> derive PROCESSOR from ""
esr> # FOOFEATURE is boolean; we look at the return status from
esr> derive FOOFEATURE from ""

I think this is cool.

esr> (kbuild people, this is one reason I want ifdefs gone from the
esr> makefiles. The autoconfigurator, whether it's Giacomo's or not,
esr> should be able to pass FOO=n to tell CML2 that a given feature is
esr> definitely not present.)

Yeah, we have to make an essential transition from 3-valued logic
("y"/"m"/"n" in some contexts and "y"/"m"/NULL in other contexts) to
4-valued logic ("y"/"m"/"n"/NULL).

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

This archive was generated by hypermail 2b29 : Sun Dec 31 2000 - 21:00:09 EST