From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Ashish Dalela <ashish.dalela@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Error while building a custom image
Date: Thu, 12 Sep 2013 16:12:32 +0100 [thread overview]
Message-ID: <2226787.84MgiCFZLh@helios> (raw)
In-Reply-To: <CABhkJRc+Ae1oYAP8821rYU8z0d5C9cHpoXVXL3vXdVnzSbx2jA@mail.gmail.com>
On Thursday 12 September 2013 19:31:59 Ashish Dalela wrote:
> On Thu, Sep 12, 2013 at 7:27 PM, Nicolas Dechesne <
> nicolas.dechesne@linaro.org> wrote:
> > On Thu, Sep 12, 2013 at 3:52 PM, Ashish Dalela
> > <ashish.dalela@gmail.com>wrote:
> >> I tried a small change. I removed the packagegroup entry and added the
> >> following to meta/recipes-extended/images/core-image-basic.bb
> >>
> >> IMAGE_INSTALL += "tpmc"
> >>
> >> Now, when I do a bitbake core-image-basic, I get this error:
> >>
> >> *Error: tpmc not found in the base feeds (qemux86 i586 i486 i386 x86
> >> noarch any all).*
> >> *
> >> *
> >> Can someone please help? It's probably something quite simple but I'm not
> >> getting it.
> >
> > did you add your layer to BBLAYERS in conf/bblayer.conf file?
> >
> > does "bitbake tpmc" actually build your recipe?
>
> Yes, bitbake tpmc is successful.
>
> Also, I added my layer to the BBLAYERS in the build/conf/bblayers.conf file.
Without further details it sounds like a "tpmc" package is being provided by a
recipe, but when it came to packaging for that recipe, the "tpmc" package was
empty. Check that the "tpmc" recipe has appropriate PACKAGES / FILES values
and that files are being installed into the correct paths within in do_install.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-09-12 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 11:22 Error while building a custom image Ashish Dalela
2013-09-12 13:52 ` Ashish Dalela
2013-09-12 13:57 ` Nicolas Dechesne
2013-09-12 14:01 ` Ashish Dalela
2013-09-12 15:12 ` Paul Eggleton [this message]
2013-09-13 5:37 ` Ashish Dalela
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=2226787.84MgiCFZLh@helios \
--to=paul.eggleton@linux.intel.com \
--cc=ashish.dalela@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.