linux/poky.git/meta/files, branch 2.2_M2

classes/populate_sdk_ext: eliminate double execution on install

2016-07-08T08:57:23+00:00

Use the new BB_SETSCENE_ENFORCE functionality to avoid having to run bitbake twice on installing the extensible SDK - we can now do it all in one invocation which not only takes less time, but we should also get more meaningful errors for some types of failure, in particular where downloading from an sstate mirror fails. One result of this change is that you get the errors printed on the console during normal output rather than this going to the preparing_build_system.log file first. In OE-Core revision 227d2cbf9e0b8c35fa6644e3d72e0699db9607fa, we changed to always print the contents of preparing_build_system.log on failure, but now at least the error contents of that log is duplicated. Besides, I intentionally didn't print out the contents of that log during normal usage because it's quite verbose - the bug that we were attempting to fix was about not getting this information when seeing failures in the automated tests, thus I've moved printing the log to the test handling code instead. Part of the implementation of [YOCTO #9367]. (From OE-Core rev: e1390c1ef85862b91b067ab24f3c06ca506155ad) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

toolchain-shar-extract.sh: allow TERM through into SDK installer env

2016-07-08T08:57:23+00:00

In order to show the task progress during the extensible SDK installation, knotty needs to know it is using a terminal it can support the "interactive" mode on (i.e. ncurses can be used), which means it needs access to the TERM variable value, so allow that through into the cleaned environment within the SDK installation script. Part of the implementation for [YOCTO #9613]. (From OE-Core rev: a8f11bc5ce07114b9ec7da7ad48da62e2026cd74) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

scripts: Replace basestring -> str for python3

2016-06-02T07:24:01+00:00

Python 3 doesn't have basestring type as all string are unicode strings. (From OE-Core rev: e8cfab060f4ff3c4c16387871354d407910e87aa) Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie

bitbake.conf/toolchain-shar-extract: Use en_US.UTF-8 as locale

2016-05-21T21:26:33+00:00

Under python 3, if we spawn python processes, we need to have a UTF-8 locale, else python's file access methods will use ascii. You can't change that mode once the interpreter is started so we have to ensure a locale is set. Ideally we'd use C.UTF-8 since OE already forces the C locale but not all distros support that and we need to set something so en_US.UTF-8 seems as standard we we can get. This matches the change in bitbake revision 8902c29638411d312e6fc4a197707e5742652e15 Also set this into the environment used when installing SDKs since python can be run and we need to ensure we use a standardised locale which is available from things like buildtools-tarball. (From OE-Core rev: 833d4c0fe804a1f7524b3d4b75cbcdd65c31ddac) Signed-off-by: Richard Purdie

ext-sdk-prepare.py: exclude do_rm_work from unexpected output; create unit test

2016-04-18T15:28:21+00:00

When installing the esdk with INHERIT += "rm_work", the script complains about do_rm_work as unexpected output from the bitbake run. This patch ignores any output lines with do_rm_work and further refactors the output comparison into its own function creates a new unit test to verify the fix. The unit test can be run direct from the command line or via oe-selftest. [YOCTO #9019] (From OE-Core rev: d41930e1daa933cf4bf063fa79a2e8fc9129e1b1) Signed-off-by: Bill Randle Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

fs-perms.txt: fix ROOT_HOME's permission

2016-04-15T05:59:44+00:00

It should be 0700 rather than 0755. Reported-by: Charles Chan (From OE-Core rev: 37aac647d510557323083c77c3114476440a325d) Signed-off-by: Robert Yang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

Revert "fs-perms.txt: fix ROOT_HOME's permission"

2016-04-15T05:59:43+00:00

This reverts commit eeae2ac4887298bcbab0e105798818414686dc97. Signed-off-by: Richard Purdie

fs-perms.txt: fix ROOT_HOME's permission

2016-04-14T09:58:34+00:00

It should be 0700 rather than 0755. Reported-by: Charles Chan (From OE-Core rev: 4ac2e5493671b198e562732e5fd8f525247527e4) Signed-off-by: Robert Yang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

toolchain-shar-extract.sh: ensure all_proxy is allowed through

2016-03-31T22:01:37+00:00

all_proxy is referred to by oe-git-proxy so ensure it is allowed through into the installer environment in case the extensible SDK install process needs to query a remote git repository. (From OE-Core rev: 65efec4cca9926b217b07c429a130088a9b8e2f6) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

oe-publish-sdk: exclude sstate-cache if publishing minimal SDK

2016-03-31T22:01:37+00:00

If SDK_EXT_TYPE is set to "minimal" then the SDK won't contain many sstate artifacts, and you're required to set up an sstate mirror in this case anyway so there's no point publishing the "stub" sstate-cache directory from within the SDK since it won't be useful for update purposes and may be confused with the real sstate-cache. There is however a possibility that people might publish the real sstate-cache directory under the same output directory provided to oe-publish-sdk, thus deleting it after extracting (as we were doing with other files we wanted to clean up at the end) would be problematic, besides which extracting it and then deleting it is wasteful. Thus, introduce a "-p" command line option to the SDK installer that we can use to tell tar not to extract the items we don't want when publishing. This has the added benefit of mostly keeping references to these in the place they belong i.e. in populate_sdk_ext.bbclass. (From OE-Core rev: 774b85d42db1d81936d4e4af4f6fb2c57cb51d2c) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie