From: Bob Cochran <yocto@mindchasers.com>
To: yocto@yoctoproject.org
Subject: Re: How to debug dependency/setscene/sstate issues
Date: Sat, 01 Nov 2014 09:08:15 -0400 [thread overview]
Message-ID: <5454DB3F.9080209@mindchasers.com> (raw)
In-Reply-To: <30C2D590D16A5C46ADFE6521910377984114ED96@AZ-US1EXMB03.global.avaya.com>
Won't Toaster give you the insight you seek?
I still need to ramp up on mastering it, but I was hoping it would help
with this sort of thing.
On 11/01/2014 08:08 AM, Vuille, Martin (Martin) wrote:
> I am using Poky daisy / Yocto 1.6.1
>
> Occasionally, when building a custom image or SDK after changing
>
> a package recipe or package content, I find that the do_rootfs task is not
>
> executed for the image or the do_populate_sdk task is not executed
>
> for the sdk.
>
> There are custom classes, packages, packagegroups involved, so it is
>
> possible, nay likely, that the problem is something I did or should’ve
>
> done but didn’t.
>
> How to approach this problem?
>
> Because the problem is intermittent, I usually won’t realize there was
>
> a problem until after bitbake is done and didn’t build what I expected.
>
> Is there a way to retrospectively review bitbake’s decision-making?
>
> Or do I need to run with –DDD all the time?
>
> MV
>
>
>
next prev parent reply other threads:[~2014-11-01 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 12:08 How to debug dependency/setscene/sstate issues Vuille, Martin (Martin)
2014-11-01 13:08 ` Bob Cochran [this message]
2014-11-01 13:45 ` Vuille, Martin (Martin)
2014-11-03 14:11 ` Barros Pena, Belen
2014-11-03 14:22 ` Vuille, Martin (Martin)
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=5454DB3F.9080209@mindchasers.com \
--to=yocto@mindchasers.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.