lkml.org 
[lkml]   [2010]   [Jun]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [RFC PATCH 1/3] kbuild: Warn on selecting symbols with unmet direct dependencies
    From
    Date
    On Fri, 2010-06-11 at 21:31 +0100, Randy Dunlap wrote:
    > On Tue, 08 Jun 2010 17:25:57 +0100 Catalin Marinas wrote:
    >
    > > The "select" statement in Kconfig files allows the enabling of options
    > > even if they have unmet direct dependencies (i.e. "depends on" expands
    > > to "no"). Currently, the "depends on" clauses are used in calculating
    > > the visibility but they do not affect the reverse dependencies in any
    > > way.
    > >
    > > The patch introduces additional tracking of the "depends on" statements
    > > and prints a warning on selecting an option if its direct dependencies
    > > are not met.
    >
    > Can these messages (on linux-next-20100611) be modified to include the
    > kconfig symbol that is causing them?
    >
    > warning: (IP_VS_PROTO_ESP && NET && NETFILTER && IP_VS ||
    > IP_VS_PROTO_AH && NET && NETFILTER && IP_VS) selects
    > IP_VS_PROTO_AH_ESP which has unmet direct dependencies (UNDEFINED)
    > warning: (SCx200_GPIO && SCx200 || PC8736x_GPIO && X86) selects
    > NSC_GPIO which has unmet direct dependencies (X86_32)
    >
    > Ah! It's the first symbol listed in each "phrase":

    (sorry for the delay)

    It is usually the first symbol though kbuild does some expression
    reduction when calculating the dependencies and I can't guarantee that
    it is always the case. It's probably for someone who understands kbuild
    better then me to make the output easier to read.

    --
    Catalin



    \
     
     \ /
      Last update: 2010-06-16 18:35    [W:0.019 / U:0.800 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site