From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Zafrullah Syed <zafrullahmehdi@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Hello world-Checksum error
Date: Tue, 04 Jun 2013 11:58:41 +0100 [thread overview]
Message-ID: <8731013.X4s1gPWXY4@helios> (raw)
In-Reply-To: <CAAGt+t3MbEC=vDykz0djfm3U4b++OtQLADFOeUz=sCwuospR4A@mail.gmail.com>
On Tuesday 04 June 2013 12:42:12 Zafrullah Syed wrote:
> previously, I successfully build *gumstix-console-image* and I have created
> *meta-bebot* folder for my recipe.
>
> My Yocto tree as follows:
>
> Yocto
> --build
> --conf
> --bblayers.conf ( I added /home/siguser/yocto2013-05-08/poky/*
> meta-bebot* \ ) path
> --local.conf ( I added IMAGE_INSTALL_append = " hello" ) under
> *Additional
> image features*
> --downloads
> --tmp
> --
> --
>
> --poky
> --bitbake
> --build
> --documentation
> --meta
> --*meta-bebot*
> * --conf*
> * --bblayers.conf *(I added /home/siguser/yocto2013-05-08/poky/*
> meta-bebot* \ ) path
If I understand correctly from the above that you have put bblayers.conf in
conf/ under your meta-bebot layer, that is not correct. bblayers.conf needs to
be under conf/ in your build directory as usual.
> * --layer.conf *(I added BBFILE_COLLECTIONS += "*meta-bebot*"
> BBFILE_PATTERN_*meta-bebot* :=
> "^${LAYERDIR}/"
> BBFILE_PRIORITY_*meta-bebot* =
> "7" )
Are you also extending BBFILES and BBPATH in your meta-bebot/conf/layer.conf?
> * --recipes-bebot*
> * --hello*
> * --hello.bb*
> --meta-gumstix
> --meta-gumstix-extras
> --meta-hob
> --meta-openembedded
> --
> --remaining other folders..
>
>
> When I try to build image *bitbake gumstix-console-image*
> again it throws this error: *ERROR: Nothing PROVIDES
> 'gumstix-console-image'*
BitBake uses BBFILES to find recipes; each layer's layer.conf typically extends
BBFILES to find the recipes within the layer. If you are receiving this error
it means (as you might expect) that BitBake cannot find a provider for the
specified target. This is either because your bblayers.conf no longer adds the
path to meta-gumstix to BBLAYERS, or because BBFILES is being reset so that it
no longer includes the path within meta-gumstix to find the gumstix-console-
image recipe. Please check that you don't have a duplicate bblayers.conf (as
mentioned above) and that your meta-bebot/conf/layer.conf is appropriately
extending BBFILES (see other layers for examples).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-06-04 10:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 11:46 Hello world-Checksum error Zafrullah Syed
2013-05-28 11:57 ` Satya Swaroop Damarla
2013-05-28 12:03 ` Zafrullah Syed
2013-05-28 12:05 ` Usman, Fahad
2013-05-28 12:14 ` Paul Eggleton
2013-05-28 12:32 ` Zafrullah Syed
2013-05-28 12:36 ` Erik Botö
2013-05-28 13:45 ` Zafrullah Syed
2013-05-28 13:54 ` Paul Eggleton
2013-06-04 10:42 ` Zafrullah Syed
2013-06-04 10:58 ` Paul Eggleton [this message]
2013-06-04 13:19 ` Zafrullah Syed
2013-06-04 13:26 ` Paul Eggleton
2013-06-04 13:42 ` Zafrullah Syed
2013-06-04 13:57 ` Paul Eggleton
2013-06-04 19:45 ` Zafrullah Syed
2013-06-04 20:01 ` Michael Stickel
2013-06-04 16:19 ` michael
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=8731013.X4s1gPWXY4@helios \
--to=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.org \
--cc=zafrullahmehdi@gmail.com \
/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.