From: "Adam J. Richter" <adam@yggdrasil.com>
To: linux-kernel@vger.kernel.org
Subject: linux-2.4.6-pre6: numerous dep_{bool,tristate} $CONFIG_ARCH_xxx bugs
Date: Fri, 29 Jun 2001 07:10:51 -0700 [thread overview]
Message-ID: <200106291410.HAA10170@baldur.yggdrasil.com> (raw)
The Config.in files in linux-2.4.6-pre6 have at least 28 cases
where a dep_bool or dep_tristate of the following form:
dep_bool CONFIG_SOMETHING $CONFIG_ARCH_somearch
The problem with this is that, unlike most configuration variables,
the $CONFIG_ARCH_xxxx variables are often not set to "n" when they are
not selected (they are often just not defined, for example, when they
are archectures for a completely different CPU type). When those variables
are not defined, that is essentially equivalent to passing "y" to dep_bool,
and the user is incorrectly asked about these facilities.
I will put together patch to convert this to ugly but correct
"if then; ... ; fi" statements later today if nobody has any better
suggestions.
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
next reply other threads:[~2001-06-29 14:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 14:10 Adam J. Richter [this message]
2001-06-29 14:21 ` Keith Owens
2001-06-29 14:30 ` Russell King
2001-06-29 14:41 ` Keith Owens
2001-06-29 15:19 ` Alan Cox
2001-06-29 14:30 ` Jeff Garzik
2001-06-30 4:35 Adam J. Richter
2001-06-30 7:26 ` Alan Cox
2001-06-30 9:20 ` Russell King
2001-06-30 11:43 ` Alan Cox
2001-06-30 11:58 ` Russell King
2001-06-30 12:01 ` Alan Cox
2001-06-30 12:02 ` Russell King
2001-06-30 11:45 ` Keith Owens
2001-06-30 12:10 ` Russell King
2001-06-30 4:40 Adam J. Richter
2001-06-30 7:23 ` Alan Cox
2001-06-30 9:38 Adam J. Richter
2001-06-30 13:32 Adam J. Richter
2001-06-30 14:57 Adam J. Richter
2001-06-30 15:01 ` Russell King
2001-07-01 2:39 ` Keith Owens
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=200106291410.HAA10170@baldur.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.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®