mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arnaud Lacombe <lacombar@gmail.com>
To: Jesper Juhl <jj@chaosbits.net>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
	Michal Marek <mmarek@suse.cz>
Subject: Re: Lots of 'warning: <foo> selects <bar> which has unmet direct dependencies <baz>' with latest git tree
Date: Wed, 10 Nov 2010 15:09:11 -0500	[thread overview]
Message-ID: <AANLkTinBuzRmmZh03k5Ln92eh2O2K72OsMTOgQ_=JjBM@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1011102021340.625@swampdragon.chaosbits.net>

Hi,

[Roman Zippel removed from CC list, Michal Marek added.]

On Wed, Nov 10, 2010 at 2:25 PM, Jesper Juhl <jj@chaosbits.net> wrote:
> remote: Counting objects: 1798826, done.
> remote: Compressing objects: 100% (276733/276733), done.
> remote: Total 1798826 (delta 1506575), reused 1798414 (delta 1506266)
> Receiving objects: 100% (1798826/1798826), 353.05 MiB | 1.02 MiB/s, done.
> Resolving deltas: 100% (1506575/1506575), done.
> [jj@dragon src]$ cd linux-2.6
> [jj@dragon linux-2.6]$ make allyesconfig
> scripts/kconfig/conf --allyesconfig Kconfig
> warning: (VIDEO_BT848 && MEDIA_SUPPORT && VIDEO_CAPTURE_DRIVERS && VIDEO_DEV && PCI && I2C && VIDEO_V4L2 && INPUT && VIDEO_IR && VIDEO_HELPER_CHIPS_AUTO) selects VIDEO_TVAUDIO which has unmet direct dependencies (MEDIA_SUPPORT && VIDEO_CAPTURE_DRIVERS && !VIDEO_HELPER_CHIPS_AUTO && VIDEO_V4L2 && I2C)
> [...]
> warning: (VIDEO_IVTV && MEDIA_SUPPORT && VIDEO_CAPTURE_DRIVERS && VIDEO_V4L2 && PCI && I2C && INPUT && VIDEO_IR) selects VIDEO_UPD64083 which has unmet direct dependencies (MEDIA_SUPPORT && VIDEO_CAPTURE_DRIVERS && !VIDEO_HELPER_CHIPS_AUTO && VIDEO_V4L2 && I2C)
>
This is a known issue, there is patches pending for most of them.

Michal ?

 - Arnaud

      parent reply	other threads:[~2010-11-10 20:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 19:25 Jesper Juhl
2010-11-10 19:53 ` Justin P. Mattock
2010-11-10 20:09 ` Arnaud Lacombe [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='AANLkTinBuzRmmZh03k5Ln92eh2O2K72OsMTOgQ_=JjBM@mail.gmail.com' \
    --to=lacombar@gmail.com \
    --cc=jj@chaosbits.net \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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®