All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: varun bhatnagar <varun292006@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Yocto Layers not getting recognized by bitbake
Date: Thu, 27 Jun 2013 21:25:38 +0100	[thread overview]
Message-ID: <2897880.FC0dZLhceG@helios> (raw)
In-Reply-To: <CAGxOggG7R-5rLHg3H_WH9wtgSnf0EZfRAYs2jtQvGK+DeQfTiA@mail.gmail.com>

On Thursday 27 June 2013 23:28:05 varun bhatnagar wrote:
>  Thanks a ton Paul and Saul for the reply. Your suggestion worked. :)
> But after building my recipe file I executed bitbake -k core-image-minimal
> and I got the following error:
> 
> NOTE: Resolving any missing task queue dependencies
> Missing or unbuildable dependency chain was: ['app-ea']
> ERROR: Nothing RPROVIDES 'app-ea' (but
> /local/varun/poky-yocto-1.4-m3/meta/recipes-core/images/
> core-image-minimal.bb RDEPENDS on or otherwise requires it)
> NOTE: Runtime target 'com-ea' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['test-ea']
> ERROR: Nothing RPROVIDES 'tipcutils' (but
> /local/varun/poky-yocto-1.4-m3/meta/recipes-core/images/
> core-image-minimal.bb RDEPENDS on or otherwise requires it)
> NOTE: Runtime target 'tipcutils' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['tipcutils']
> NOTE: Preparing runqueue
> ERROR: All buildable tasks have been run but the build is incomplete
> (--continue mode). Errors for the tasks that failed will have been printed
> above.
> 
> Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
> 
> 
> Any idea how to resolve this one?

None of "com-ea", "test-ea" or "tipcutils" are normally in core-image-minimal 
nor are they in any OE layer that I am aware of. I can only suggest that you 
might have added these to CORE_IMAGE_EXTRA_INSTALL, is that correct? If so, 
either remove these or ensure they actually exist somewhere in an enabled 
layer where that layer has BBFILES correctly set up in its conf/layer.conf file 
to match the directory structure of the layer.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-06-27 20:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17 17:08 Yocto Layers not getting recognized by bitbake varun bhatnagar
2013-06-17 17:33 ` Gary Thomas
2013-06-17 18:03   ` varun bhatnagar
2013-06-17 21:02     ` Sudhangathan B S
2013-06-18 16:28       ` varun bhatnagar
2013-06-18 16:41         ` Gary Thomas
2013-06-19 16:10           ` varun bhatnagar
2013-06-22 19:04             ` varun bhatnagar
2013-06-25 10:46               ` Paul Eggleton
2013-06-25 19:04                 ` varun bhatnagar
2013-06-25 19:13                   ` Saul Wold
2013-06-27 17:58                     ` varun bhatnagar
2013-06-27 20:25                       ` Paul Eggleton [this message]
2013-06-29 18:35                         ` varun bhatnagar
2013-07-01  9:48                           ` Paul Eggleton
2013-07-12 18:23                             ` varun bhatnagar

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=2897880.FC0dZLhceG@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=varun292006@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.