All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Paul Sokolovsky <pmiscml@gmail.com>
Cc: openembedded-devel@openembedded.org
Subject: Re: Another weird case of PACKAGES_DYNAMIC and task deps, it seems
Date: Mon, 07 Jan 2008 20:44:24 +0000	[thread overview]
Message-ID: <1199738665.4680.66.camel@localhost.localdomain> (raw)
In-Reply-To: <116173998.20080107221856@gmail.com>

On Mon, 2008-01-07 at 22:18 +0200, Paul Sokolovsky wrote:
> Monday, January 7, 2008, 1:47:23 AM, you wrote:
> > So the question is why doesn't your test case have this (I'm assuming it
> > doesn't). My best guess is that the kernel .bb file in question alters
> > DEPENDS and that update-modules isn't really in DEPENDS. Which
> > kernel .bb file serves the machine in question?
> 
>   Gotcha! I tried
> 
>  MACHINE=h4000 bitbake initramfs-image -g
> 
> and it gives the same matches as you quote below. But
> 
>  MACHINE=collie bitbake initramfs-image -g
> 
> Gives zero matches for update-modules. I don't try to investigate
> further now, as you probably know better about it ;-).

My money is on:

DEPENDS_collie += "bc-native"

in linux-rp.inc. Try removing that...

Cheers,

Richard





  reply	other threads:[~2008-01-07 20:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-04  1:17 Another weird case of PACKAGES_DYNAMIC and task deps, it seems Paul Sokolovsky
2008-01-06 23:47 ` Richard Purdie
2008-01-07 20:18   ` Paul Sokolovsky
2008-01-07 20:44     ` Richard Purdie [this message]
2008-01-07 21:47       ` Richard Purdie
2008-01-07 22:52         ` Metadata Q/A (was: Another weird case of PACKAGES_DYNAMIC and task deps, it seems) Michael 'Mickey' Lauer
2008-01-08 11:14           ` Richard Purdie
2008-01-08 12:48             ` Paul Sokolovsky
2008-01-08 12:30         ` Another weird case of PACKAGES_DYNAMIC and task deps, it seems Paul Sokolovsky

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=1199738665.4680.66.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    --cc=pmiscml@gmail.com \
    /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.