From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: what means duplicate "config" entries in Kconfig file?
Date: Wed, 9 Apr 2003 12:43:12 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0304091237490.28112-100000@dell> (raw)
In-Reply-To: <Pine.LNX.4.44.0304091818470.12110-100000@serv>
On Wed, 9 Apr 2003, Roman Zippel wrote:
> On Wed, 9 Apr 2003, Robert P. J. Day wrote:
> > i'm not sure what it means to have two config entries with
> > identical symbols. can someone clarify this? i'm just confused
> > (which should not come as a surprise at this point).
>
> You can have as much entries as you want, the only limit is that you can
> only have one user prompt per config entry and the type must not conflict.
> This example could have been done with a single entry and this is usually
> prefered to keep it more compact, but you don't have to.
not to belabor this, but what does it mean when the two dependencies
are mutually exclusive, as in the example i provided:
-----------------------
config MCA
bool "MCA support"
depends on !(X86_VISWS || X86_VOYAGER)
help
MicroChannel Architecture is found in some IBM PS/2 machines and
laptops. It is a bus system similar to PCI or ISA. See
<file:Documentation/mca.txt> (and especially the web page given
there) before attempting to build an MCA bus kernel.
config MCA
depends on X86_VOYAGER
default y if X86_VOYAGER
---------------------
the two options X86_VISWS and X86_VOYAGER are simple "bool"s
representing the (radio-box) subarchitecture type.
the first seems to represent a dependency of *neither* of those
two listed options, while the second config *depends* on one of
them.
how exactly do you reconcile what looks like contradictory
dependencies for the same config entry?
rday,
wondering just how badly he's embarrassing himself by now ...
next prev parent reply other threads:[~2003-04-09 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 12:30 Robert P. J. Day
2003-04-09 16:08 ` Randy.Dunlap
2003-04-09 16:23 ` Roman Zippel
2003-04-09 16:43 ` Robert P. J. Day [this message]
2003-04-09 19:54 ` Roman Zippel
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=Pine.LNX.4.44.0304091237490.28112-100000@dell \
--to=rpjday@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®