public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kconfig: report select on a depending option
Date: Thu, 18 Mar 2010 11:12:22 +0100	[thread overview]
Message-ID: <4BA1FC86.6020504@suse.cz> (raw)
In-Reply-To: <alpine.LSU.2.01.1003181015060.9334@obet.zrqbmnf.qr>

On 18.3.2010 10:21, Jan Engelhardt wrote:
> Hi,
> 
> 
> With the following combination of Kconfig config options, I can select 
> TEST_Z, which will select TEST_X, even if TEST_Y=n. It also allows for 
> awkward situations like TEST_Y=M, TEST_X=y, TEST_Z=y, which would yield 
> a link time error when X uses Y's symbols.

That's a known bug unfortunatelly
(Documentation/kbuild/kconfig-language.txt):
  Note:
        select should be used with care. select will force
        a symbol to a value without visiting the dependencies.
        By abusing select you are able to select a symbol FOO even
        if FOO depends on BAR that is not set.
        In general use select only for non-visible symbols
        (no prompts anywhere) and for symbols with no dependencies.
        That will limit the usefulness but on the other hand avoid
        the illegal configurations all over.
        kconfig should one day warn about such things.



> Is there a way to have such potential errors reported with kconfig?

No there isn't. There is a guy who wants to work on improving/rewriting
the kconfig depsolver during GSoC, let's see :). But a warning should be
easy to add now, I think.

Michal

      parent reply	other threads:[~2010-03-18 10:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18  9:21 kconfig: report select on a depending option Jan Engelhardt
2010-03-18  9:31 ` Américo Wang
2010-03-18 10:12 ` Michal Marek [this message]

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=4BA1FC86.6020504@suse.cz \
    --to=mmarek@suse.cz \
    --cc=jengelh@medozas.de \
    --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