From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: John Toomey <john.toomey@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: RPROVIDES issue
Date: Wed, 29 Feb 2012 16:18:29 +0000 [thread overview]
Message-ID: <4241171.S03hq4heSm@helios> (raw)
In-Reply-To: <4F4E4512.7000505@linux.intel.com>
On Wednesday 29 February 2012 15:32:34 John Toomey wrote:
> I am getting an error when I try to include some packages such as
> logrotate, valgrind and minicom in my configuration using "IMAGE_INSTALL
> += ... "
>
> ERROR: Nothing RPROVIDES '"minicom"' (but
> [path]/core-image-[blah].bb RDEPENDS on or otherwise requires it)
> NOTE: Runtime target '"minicom"' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['"minicom"']
> ERROR: Required build target 'core-image-small' has no buildable
> providers.
> Missing or unbuildable dependency chain was: ['core-image-[blah]',
> '"minicom"']
>
>
> I am able to build the packages individually without issue, for example
> "bitbake minicom" works fine.
>
> Can anyone help point me in the right direction?
I noticed something here which I saw earlier - there is somehow an extra set
of quotes in there i.e. it's reporting '"minicom"' instead of 'minicom'.
Having just confirmed here with the 1.1 release that when you specify something
that doesn't exist you only get one set of single quotes in the error, I
suspect that's the root of the problem in your case. How you would have got a
set of double quotes in there I don't know, though. When I do IMAGE_INSTALL +=
"something" I don't get them here.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-02-29 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 15:32 RPROVIDES issue John Toomey
2012-02-29 16:18 ` Paul Eggleton [this message]
2012-02-29 16:44 ` John Toomey
2012-02-29 16:55 ` Paul Eggleton
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=4241171.S03hq4heSm@helios \
--to=paul.eggleton@linux.intel.com \
--cc=john.toomey@linux.intel.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.