From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Cannot satisfy the following dependencies for task-core-basic: libusb-compat (>= 0.1.3)
Date: Wed, 22 Feb 2012 12:12:12 +0000 [thread overview]
Message-ID: <1329912732.20261.110.camel@ted> (raw)
In-Reply-To: <CA+b4E8x4_cCvhUw-UgLK=9ymuoXsiih8BMZc=ts0B7Qf=oaNuQ@mail.gmail.com>
On Tue, 2012-02-21 at 18:50 -0500, Brandon Stafford wrote:
> In trying to build core-image-basic, it seems that libusb-compat
> cannot be found:
>
> | Collected errors:
> | * satisfy_dependencies_for: Cannot satisfy the following
> dependencies for task-core-basic:
> | * libusb-compat (>= 0.1.3) *
> | * opkg_install_cmd: Cannot install package task-core-basic.
> NOTE: package core-image-basic-1.0-r0: task do_rootfs: Failed
>
> However, it seems like libusb-compat should be findable:
>
> :~/oe-core/build$ ls ../meta/recipes-support/libusb/
> libusb1_1.0.8.bb libusb-compat-0.1.3 libusb-compat_0.1.3.bb
>
> Do I need to tell bitbake to look in recipes-support explicitly?
The above error looks like its from the rootfs generation and not from
bitbake itself.
The first question is did it build libusb-compat at all? Are there any
stamps for this in tmp/stamps/*/libusb-compat* or files in
tmp/work/*/libusb-compat* that would suggest that it did?
Secondly, did it place any libusb-compat package into tmp/deploy/ipk/* ?
The answers to the above questions will start to help know where to look
for the problem.
Cheers,
Richard
next prev parent reply other threads:[~2012-02-22 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 23:50 Cannot satisfy the following dependencies for task-core-basic: libusb-compat (>= 0.1.3) Brandon Stafford
2012-02-22 12:12 ` Richard Purdie [this message]
2012-02-22 16:52 ` Brandon Stafford
2012-02-22 17:47 ` Richard Purdie
2012-02-22 18:46 ` Brandon Stafford
2012-02-22 19:31 ` Richard Purdie
2012-02-22 19:45 ` Brandon Stafford
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=1329912732.20261.110.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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.