From: Randy Witt <randy.e.witt@linux.intel.com>
To: Christopher Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] populate_sdk_ext: Log the "Preparing build system" step
Date: Wed, 25 Mar 2015 10:59:39 -0700 [thread overview]
Message-ID: <5512F78B.2090800@linux.intel.com> (raw)
In-Reply-To: <CABcZANkfjcqPVHPOKZBjQYGAr2HRwmAEha1LgPM3spZ90NwxBw@mail.gmail.com>
On 03/25/2015 10:31 AM, Christopher Larson wrote:
> On Tue, Mar 24, 2015 at 5:16 PM, Randy Witt <randy.e.witt@linux.intel.com>
> wrote:
>
>> When using bitbake to do the setscene as part of sdk setup, it would be
>> useful to have a log in the case where it fails.
>>
>> The log is called preparing_build_system.log and is in the top level
>> directory of the extracted sdk.
>>
>> Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com>
>>
>
> Is this step just doing a setscene from shipped sstate, or is it intended
> to build anything from scratch? Because I've seen cases where the sstate
> isn't used as it should be, and it ends up taking ages to run real tasks.
>
It should be using the shipped sstate based on the locked-sigs.inc file. I would
expect it to fail if the signatures didn't match for some reason, but perhaps a
change went in that changed behavior.
If you see an instance where it is not using the shipped sstate, could you file
a bug or send an email? I'm really curious as to why it doesn't fail outright,
because that's the whole point of the locked-sigs.inc file.
next prev parent reply other threads:[~2015-03-25 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 0:16 [PATCH] populate_sdk_ext: Log the "Preparing build system" step Randy Witt
2015-03-25 17:31 ` Christopher Larson
2015-03-25 17:59 ` Randy Witt [this message]
2015-03-25 21:09 ` Richard Purdie
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=5512F78B.2090800@linux.intel.com \
--to=randy.e.witt@linux.intel.com \
--cc=clarson@kergoth.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox