Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: openembedded-devel@openembedded.org
Subject: Another weird case of PACKAGES_DYNAMIC and task deps, it seems
Date: Fri, 4 Jan 2008 03:17:51 +0200	[thread overview]
Message-ID: <1068494393.20080104031751@gmail.com> (raw)

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.

5. Manual explicit build of update-modules clears those errors.

   My analysis:

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".

Then, do_spli_package() kinda should set RDEPENDS for each module, but
I remember we already discussed issue that this doesn't really work
for PACKAGES_DYNAMIC ;-(.

So, any ideas how to at least work this around? I recently hit similar
issue when package_ipk.bbclass tried to execute ipkg-build before it
was staged, and that was fixed in natural way:

do_package_write_ipk[depends] = "ipkg-utils-native:do_populate_staging"

Maybe we could use that as a workaround for kernel.bbclass, so we
don't go packing modules, until update-modules' package is written.
The issue, kernel.bbclass doesn't even define proper task for that,
only a prepender, so I have no idea what to put dependency on.


     Richard, any comments?


-- 
Best regards,
 Paul                          mailto:pmiscml@gmail.com




             reply	other threads:[~2008-01-04  2:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-04  1:17 Paul Sokolovsky [this message]
2008-01-06 23:47 ` Another weird case of PACKAGES_DYNAMIC and task deps, it seems Richard Purdie
2008-01-07 20:18   ` Paul Sokolovsky
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=1068494393.20080104031751@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox