From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/15542] %( CONFIG_NO_SUCH_VAR == "n" ... %) doesn't evaluate to true
Date: Tue, 28 May 2013 18:54:00 -0000 [thread overview]
Message-ID: <bug-15542-6586-22JftkbOI9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15542-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15542
Josh Stone <jistone at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jistone at redhat dot com
--- Comment #1 from Josh Stone <jistone at redhat dot com> ---
CONFIG_NO_SUCH_VAR == "" works. In fact, this is also true for variables that
exist but are not enabled, like CONFIG_PREEMPT_RCU on F18. Are there any names
which are actually true for == "n"?
CONFIG values are either "y" for built-in, "m" for module, or else absent
altogether leading to the default std::string "".
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-05-28 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 15:55 [Bug translator/15542] New: " dsmith at redhat dot com
2013-05-28 18:54 ` jistone at redhat dot com [this message]
2016-05-26 17:39 ` [Bug translator/15542] " fche at redhat dot com
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=bug-15542-6586-22JftkbOI9@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).