From: Valdis.Kletnieks@vt.edu
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-arch@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kbuild@vger.kernel.org,
Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: kbuild: fixing the select problem
Date: Thu, 06 May 2010 12:47:07 -0400 [thread overview]
Message-ID: <28312.1273164427@localhost> (raw)
In-Reply-To: Your message of "Thu, 06 May 2010 09:17:24 EDT." <1273151844.23208.48.camel@mulgrave.site>
[-- Attachment #1: Type: text/plain, Size: 2082 bytes --]
On Thu, 06 May 2010 09:17:24 EDT, James Bottomley said:
> On Thu, 2010-05-06 at 08:47 +0200, Geert Uytterhoeven wrote:
> > On Wed, May 5, 2010 at 23:49, James Bottomley
> > <James.Bottomley@hansenpartnership.com> wrote:
> > > [Sam: I know you don't maintain kbuild anymore, but since you have the
> > > most experience, if you could find time to comment, I'd be grateful]
> > >
> > > The select problem is that the kbuild select directive will turn a
> > > symbol on without reference to its dependencies. This, in turn, means
> > > that either selected symbols must select their dependencies, or that
> > > people using select have to be aware of the selected symbol's dependency
> > > and build those dependencies into their symbol (leading to duplication
> > > and the possibility of getting the dependencies out of sync). We use
> > > select for the scsi transport classes, so we run into this problem in
> > > SCSI quite a lot.
> > >
> > > I think the correct fix is to make a symbol that selects another symbol
> > > automatically inherit all of the selected symbol's dependencies.
> >
> > What if there's a good reason the selected symbol has this dependency?
> > E.g. it depends on a critical feature not available? Like CONFIG_HAS_IOMEM?
>
> I don't quite understand the question. If a selected symbol has a
> critical dependency which is config'd to N then the build usually
> breaks ... that's what I'm calling the select problem. I thought
> CONFIG_HAS_IOMEM was usually selected by the architecture, though. In
> the new proposal, we wouldn't be able to generate the invalid
> configuration in the first place.
I think Geert is asking "If the arch says CONFIG_HAS_IOMEM=n, but some driver
does a 'select CONFIG_FOO' which then (under your proposal) forces the
value CONFIG_BAR=y, which eventually ends up with CONFIG_HAS_IOMEM=y, what
should the behavior be?"
(I suspect the right answer here is "one of the symbols is buggy and its
'select' should be a 'depends' instead", but somebody else better double-check
that conclusion - I'm hardly a Kconfig expert).
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2010-05-06 16:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 21:49 kbuild: fixing the select problem James Bottomley
2010-05-06 6:47 ` Geert Uytterhoeven
2010-05-06 6:47 ` Geert Uytterhoeven
2010-05-06 13:17 ` James Bottomley
2010-05-06 13:36 ` Geert Uytterhoeven
2010-05-06 16:47 ` Valdis.Kletnieks [this message]
2010-05-06 17:25 ` Geert Uytterhoeven
2010-05-06 17:25 ` Geert Uytterhoeven
2010-05-06 14:24 ` Michal Marek
2010-05-06 14:52 ` James Bottomley
2010-05-06 20:48 ` James Bottomley
2010-05-06 20:59 ` Randy Dunlap
2010-05-06 21:05 ` James Bottomley
2010-05-06 16:52 ` Vegard Nossum
2010-05-07 11:31 ` Catalin Marinas
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=28312.1273164427@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sam@ravnborg.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 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.