Skip to contentSkip to conversation

How do we handle autoconfiguration?

KBUILD Michael Elizabeth Chastain 1 participant 1 message Dec 27, 2000

lore
Share & tools
lore
#0 lore raw

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

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).

Michael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/