[PATCH] populate_sdk_ext: Log the "Preparing build system" step

[PATCH] populate_sdk_ext: Log the "Preparing build system" step

[Randy Witt]

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>
---
 meta/classes/populate_sdk_ext.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/populate_sdk_ext.bbclass b/meta/classes/populate_sdk_ext.bbclass
index ec1cff0..22e0ffc 100644
--- a/meta/classes/populate_sdk_ext.bbclass
+++ b/meta/classes/populate_sdk_ext.bbclass
@@ -182,7 +182,7 @@ sdk_ext_postinst() {
 	# dash which is /bin/sh on Ubuntu will not preserve the
 	# current working directory when first ran, nor will it set $1 when
 	# sourcing a script. That is why this has to look so ugly.
-	sh -c ". buildtools/environment-setup* > /dev/null && cd $target_sdk_dir/`dirname ${oe_init_build_env_path}` && set $target_sdk_dir && . $target_sdk_dir/${oe_init_build_env_path} $target_sdk_dir > /dev/null && bitbake ${SDK_TARGETS} > /dev/null" || { echo "SDK preparation failed" ; exit 1 ; }
+	sh -c ". buildtools/environment-setup* > preparing_build_system.log && cd $target_sdk_dir/`dirname ${oe_init_build_env_path}` && set $target_sdk_dir && . $target_sdk_dir/${oe_init_build_env_path} $target_sdk_dir >> preparing_build_system.log && bitbake ${SDK_TARGETS} >> preparing_build_system.log" || { echo "SDK preparation failed: see `pwd`/preparing_build_system.log" ; exit 1 ; }
 	echo done
 }
 
-- 
1.9.3

Re: [PATCH] populate_sdk_ext: Log the "Preparing build system" step

[Christopher Larson]

[-- Attachment #1: Type: text/plain, Size: 776 bytes --]

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.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

[-- Attachment #2: Type: text/html, Size: 1272 bytes --]

Re: [PATCH] populate_sdk_ext: Log the "Preparing build system" step

[Randy Witt]

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.

Re: [PATCH] populate_sdk_ext: Log the "Preparing build system" step

[Richard Purdie]

On Wed, 2015-03-25 at 10:31 -0700, 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.

Are you using http sstate mirrors out of interest?

I've been experimenting with them and there are some serious performance
issues trying to do that if there is any kind of network latency :(.

Cheers,

Richard