From: Ulf Samuelsson <ulf@emagii.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: bitbake core-image-sato fails:
Date: Fri, 09 Dec 2011 00:24:20 +0100 [thread overview]
Message-ID: <4EE14724.7010202@emagii.com> (raw)
In-Reply-To: <CAEsOVNfs+HayYVZ3Mm=k=ubnmUBeO88OKj1fKzZE0R5+Uw=6tQ@mail.gmail.com>
On 2011-12-08 22:14, McClintock Matthew-B29882 wrote:
> On Wed, Dec 7, 2011 at 10:29 AM, Ulf Samuelsson
> <openembedded-core@emagii.com> wrote:
>> Got the following error message when building core-image-sato:
>>
>> | Collected errors:
>> | * satisfy_dependencies_for: Cannot satisfy the following dependencies for
>> task-core-x11-sato:
>> | * ofono *
>> | * opkg_install_cmd: Cannot install package task-core-x11-sato.
>> NOTE: package core-image-sato-1.0-r0: task do_rootfs: Failed
>> ERROR: Task 8
>> (/home/ulf/projects/OE_atmel/sources/openembedded-core/meta/recipes-sato/images/core-image-sato.bb,
>> do_rootfs) failed with exit code '1'
> The rpm for ofono was not generated, and something in
> task-core-x11-sato depends on it. So rpm goes and tries to resolve its
> dependency (which adds other packages) and it can't find one for
> ofono. Some recipe in this task needs a DEPENDS += "ofono"
>
> -M
task-core-x11-sato contains:
NETWORK_MANAGER ?= "connman-gnome"
and connman-gnome contains references to ofono,
so this is probably a good candidate.
connman-gnome is not building at the moment, due
to the empty repo at kernel.org so I am going to
try adding it in the debug layer I have on top of OE.
BR
Ulf
prev parent reply other threads:[~2011-12-08 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 16:29 bitbake core-image-sato fails: Ulf Samuelsson
2011-12-07 16:39 ` Martin Jansa
2011-12-08 21:14 ` McClintock Matthew-B29882
2011-12-08 23:24 ` Ulf Samuelsson [this message]
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=4EE14724.7010202@emagii.com \
--to=ulf@emagii.com \
--cc=B29882@freescale.com \
--cc=openembedded-core@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.