From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Chris Tapp <opensource@keylevel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Build fails moving from 4.0.1 to 5.0.1
Date: Fri, 19 Aug 2011 09:16:38 -0700 [thread overview]
Message-ID: <1313770598.13995.115.camel@rex> (raw)
In-Reply-To: <1D7CE6A2-A65C-44F7-89F9-F66374E58B36@keylevel.com>
On Fri, 2011-08-19 at 08:29 +0100, Chris Tapp wrote:
> I've got a configuration that builds ok under 4.0.1, but when I build
> under 5.0.1 I get the following right at the end:
>
> Installing task-poky-boot (1.0-r7) to root...
> Downloading file:/home/chris/yocto/ebox3300-build/tmp/deploy/ipk/
> Vortex86DX/task-poky-boot_1.0-r7_Vortex86DX.ipk.
> Installing task-sjs (1.0-r0) to root...
> Downloading file:/home/chris/yocto/ebox3300-build/tmp/deploy/ipk/
> Vortex86DX/task-sjs_1.0-r0_Vortex86DX.ipk.
> Unknown package 'run-postinsts'.
> Collected errors:
> * satisfy_dependencies_for: Cannot satisfy the following
> dependencies for task-poky-boot:
> * tinylogin * busybox * modutils-initscripts * initscripts *
> console-tools * initscripts * udev * sysvinit * netbase * base-
> passwd *
> * opkg_install_cmd: Cannot install package task-poky-boot.
> * satisfy_dependencies_for: Cannot satisfy the following
> dependencies for task-sjs:
> * yocto-wallboard * psplash * syslinux *
> * opkg_install_cmd: Cannot install package task-sjs.
> * opkg_install_cmd: Cannot install package run-postinsts.
> ERROR: Function 'do_rootfs' failed (see ...
>
> If I look in tmp/work, it looks as if the missing dependencies have
> all been built and packaged within their work areas.
>
> I tried cleaning and rebuilding 'task-sjs', but that made no
> difference to the errors reported against it.
>
> Where should I start looking to work out what's going wrong here? Is
> it as simple as needing to add something like RDEPENDS?
This sounds like the machine specific packages are failing to be found
so it sounds like a package feed issue. Is sounds like PACKAGE_ARCHS
isn't listing everything it needs to (such as the machine name) or the
package system isn't finding a group of packages for some other reason.
Cheers,
Richard
next prev parent reply other threads:[~2011-08-19 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 7:29 Build fails moving from 4.0.1 to 5.0.1 Chris Tapp
2011-08-19 16:16 ` Richard Purdie [this message]
2011-08-19 19:43 ` Chris Tapp
2011-08-19 20:49 ` Richard Purdie
2011-08-19 20:58 ` Chris Tapp
2011-08-19 21:22 ` Richard Purdie
2011-08-21 9:19 ` Chris Tapp
2011-08-21 11:20 ` Chris Tapp
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=1313770598.13995.115.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=opensource@keylevel.com \
--cc=yocto@yoctoproject.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.