From: Paul Sokolovsky <pmiscml@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Another weird case of PACKAGES_DYNAMIC and task deps, it seems
Date: Mon, 7 Jan 2008 22:18:56 +0200 [thread overview]
Message-ID: <116173998.20080107221856@gmail.com> (raw)
In-Reply-To: <1199663243.4658.71.camel@localhost.localdomain>
Hello Richard,
Monday, January 7, 2008, 1:47:23 AM, you wrote:
> Hi Paul,
> On Fri, 2008-01-04 at 03:17 +0200, Paul Sokolovsky wrote:
>> Hello openembedded-devel,
>>
>> Situation (as reported by Thomas Kunze on IRC):
>> 1. Build from scratch
>> 2. Kernel has been built.
>> 3. Bitbake of initramfs-image.
>> 4. Failure with:
>>
>> | ERROR: Cannot satisfy the following dependencies for initramfs-module-loop:
>> | update-modules update-modules update-modules
>> | ERROR: Cannot satisfy the following dependencies for initramfs-module-nfs:
>> | update-modules
>>
>> initramfs-module-* doesn't Depends: on update-modules directly, but
>> they Suggest: some kernel-module-* which in turn Depends: on
>> update-modules.
> Hmm. Which kernel is this with?
Thomas wanted to build adhoc bootloading initramfs for Collie, so I
assume he built for it.
>> kernel.bbclass has:
>>
>> DEPENDS += "virtual/${TARGET_PREFIX}depmod-${@get_kernelmajorversion('${PV}')} virtual/${TARGET_PREFIX}gcc${KERNEL_CCSUFFIX} update-modules"
>>
>> But as we now know, that doesn't mean there will be package written
>> for update-modules, only that it will be "built".
> Nearly but not quite. rootfs_ipk.bbclass says:
> do_rootfs[recrdeptask] += "do_package_write_ipk"
> This means that every RDEPENDS, RRECOMMENDS and DEPENDS is followed and
> the package_write_ipk for every package found must have run.
> I just did a:
> "bitbake poky-image-minimal -g; cat task-depends.dot | grep update-modules"
> which gave me this list:
> "poky-image-minimal.do_rootfs" -> "update-modules.do_populate_staging"
> "poky-image-minimal.do_rootfs" ->
> "update-modules.do_package_write_ipk"
> "linux.do_package" -> "update-modules.do_package"
> "linux.do_configure" -> "update-modules.do_populate_staging"
> and a load of other dependencies which we aren't interested in. The key
> line is:
> "poky-image-minimal.do_rootfs" ->
> "update-modules.do_package_write_ipk"
> 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 ;-).
> Cheers,
> Richard
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2008-01-08 0:33 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 [this message]
2008-01-07 20:44 ` Richard Purdie
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=116173998.20080107221856@gmail.com \
--to=pmiscml@gmail.com \
--cc=openembedded-devel@lists.openembedded.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.