From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: esr@snark.thyrsus.com, torvalds@transmeta.com
Cc: anedah-9@sm.luth.se, cate@student.ethz.ch,
kaih@khms.westfalen.de, linux-kbuild@torque.net,
linux-kernel@vger.kernel.org, timw@splhi.com
Subject: Re: [KBUILD] How do we handle autoconfiguration?
Date: Tue, 26 Dec 2000 16:52:15 -0800 [thread overview]
Message-ID: <200012270052.QAA29361@craftsman.cygnus.com> (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 majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-27 1:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 0:52 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-26 23:18 How do we handle autoconfiguration? Eric S. Raymond
2000-12-27 10:31 ` [KBUILD] " Giacomo A. Catenazzi
2000-12-26 23:13 Eric S. Raymond
2000-12-27 11:14 ` [KBUILD] " Giacomo A. Catenazzi
2000-12-27 14:27 ` Giacomo A. Catenazzi
2000-12-27 16:10 ` Eric S. Raymond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200012270052.QAA29361@craftsman.cygnus.com \
--to=chastain@cygnus.com \
--cc=anedah-9@sm.luth.se \
--cc=cate@student.ethz.ch \
--cc=esr@snark.thyrsus.com \
--cc=kaih@khms.westfalen.de \
--cc=linux-kbuild@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=timw@splhi.com \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.