From: Elvis Dowson <elvis.dowson@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Yocto Discussion Mailing List <yocto@yoctoproject.org>
Subject: Re: Dependency walk for busybox recipe
Date: Sun, 16 Sep 2012 20:09:10 +0400 [thread overview]
Message-ID: <5055F9A6.20709@gmail.com> (raw)
In-Reply-To: <CAMKF1sr9zgFJMrhBM_xdVPMM_zhnQCzjxYanub6O7NFG4w1Ohg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1848 bytes --]
On 09/16/2012 07:54 AM, Khem Raj wrote:
> On Sat, Sep 15, 2012 at 10:59 AM, Elvis Dowson <elvis.dowson@gmail.com> wrote:
>> So I added busybox-1.19.4 recipe back into my poky master branch, and the resulting size of the busybox-1.19.4 /bin/busybox or /bin/sh executable is 604.2 kb.
> make sure that .config of busybox has not changed even if you have
> same version backported
I've made sure that the defconfig files used in the recipe are
identical. The only addition that I notice now, is that the recent
rework done to task-core-boot, resulting in it being renamed as
packagegroup-core-boot.bb adds the following extra line:
${@base_contains("MACHINE_FEATURES", "rtc", "busybox-hwclock", "", d)} \
My virtex5.conf machine features entry does not specify an rtc,
MACHINE_FEATURES = "kernel26 apm ext2 ext3 vfat ethernet keyboard screen
serial"
yet the current poky master attempts to pull it in:
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'busybox-hwclock' (but
/tool/yocto/poky/meta/recipes-core/packagegroups/packagegroup-core-boot.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'busybox-hwclock' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['busybox-hwclock']
NOTE: Runtime target 'packagegroup-core-boot' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['packagegroup-core-boot',
'busybox-hwclock']
ERROR: Required build target 'core-image-minimal' has no buildable
providers.
Missing or unbuildable dependency chain was: ['core-image-minimal',
'packagegroup-core-boot', 'busybox-hwclock']
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
Is this a bug? Is the rtc being added from somewhere else? Should this
be happening?
Best regards,
Elvis Dowson
[-- Attachment #2: Type: text/html, Size: 2948 bytes --]
next prev parent reply other threads:[~2012-09-16 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 17:59 Dependency walk for busybox recipe Elvis Dowson
2012-09-16 3:54 ` Khem Raj
2012-09-16 16:09 ` Elvis Dowson [this message]
2012-09-16 18:31 ` Paul Eggleton
2012-09-17 16:32 ` Elvis Dowson
2012-09-17 17:41 ` Burton, Ross
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=5055F9A6.20709@gmail.com \
--to=elvis.dowson@gmail.com \
--cc=raj.khem@gmail.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.