linux/poky.git/meta/classes, branch uninative-2.1

kernel: specify dependencies for compilation for config tasks

2018-06-12T22:34:24+00:00

With recent kernels (i.e. 4.17+) the configuration phase of the kernel will check for capabilities/options of the compiler for CVE and other mitigation support. For a general kernel, we want to ensure that CC is fully defined when the config targets are invoked (so the proper compiler will be checked). For linux-yocto, we also need to specify the compiler/tools dependencies for the configme task since it executes before configure and hence the main kernel build DEPENDS will not always be in the sysroot before it executes. Without those dependencies the kernel will be incorrectly configured (i.e. bison is missing) or the configuration will fail the mitigation tests. [YOCTO #12757] (From OE-Core rev: ff1bdd75d50f0ebac3d599e461685ace29559a82) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

toolchain-scripts: pass env to post-relocate

2018-06-07T07:52:55+00:00

It's useful for the post-relocate scripts to be able to see the SDK environment, for example to see the values of CC, CXX etc. in order to dynamically generate toolchain files. To enable this, source the SDK environment script prior to calling the relocate scripts. (From OE-Core rev: adcf69ee3310171580c28e141fec6997b1f06da4) Signed-off-by: Martin Kelly Signed-off-by: Richard Purdie

toolchain-scripts: print post-relocate error

2018-06-07T07:52:55+00:00

Currently, if a post-relocate script fails, it fails silently. We should be louder about this, as it likely indicates a broken SDK. Print a message if a post-relocate script fails. (From OE-Core rev: 369b5f3f98f8455c79731621cc669ad1948e2022) Signed-off-by: Martin Kelly Signed-off-by: Richard Purdie

toolchain-scripts: allow non-sh post-relocate

2018-06-07T07:52:55+00:00

Currently, we look only for scripts matching *.sh, which means we can't write post-relocate scripts in other languages. Expand this to allow any type of script. (From OE-Core rev: 5569a6ec6d3c4358719350cac88afa69a76097a8) Signed-off-by: Martin Kelly Signed-off-by: Richard Purdie

toolchain-scripts: retab file

2018-06-07T07:52:55+00:00

A function is uses a mix of spaces and tabs. The rest of the file uses tabs, so switch to tabs uniformly. (From OE-Core rev: 693daaac7399a5a7665cd3bcbc915ff93db36db5) Signed-off-by: Martin Kelly Signed-off-by: Richard Purdie

dropbear: drop run time detection of read-only rootfs

2018-06-04T14:15:00+00:00

Previously, when dropbear was started via its init script, relocation of DROPBEAR_RSAKEY_DIR to support read-only rootfs was handled at run time from within the init script. Update the init script to take advantage of the read-only rootfs config setup by read_only_rootfs_hook() and therefore be consistent with startup under systemd (where relocation of DROPBEAR_RSAKEY_DIR is handled by the read_only_rootfs_hook() at build time). (From OE-Core rev: 4990f87b2f6a8b30c8d1c767636e7f5527f595ba) Signed-off-by: Andre McCurdy Signed-off-by: Richard Purdie

testimage.bbclass: move codes into testimage_main

2018-06-04T14:15:00+00:00

testimage-auto is expected to run testimage task's codes automatically. But in fact, it's currently missing some codes, including testimage_sanity and create_rpm_index. This leads to the problem of unexpected runtime failure of test_dnf_makecache. The error message is as below. RESULTS - dnf.DnfRepoTest.test_dnf_makecache - Testcase 1744: ERROR This error is caused by the fact that create_rpm_index is not executed before running the tests. There's no reason why such codes should not be in testimage_main, so move them into it. (From OE-Core rev: fa7ba486ded13907f63f9300f66350ba2835a3f7) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

testimage.bbclass: also check 'auto' to create rpm index

2018-06-04T14:15:00+00:00

Having 'auto' in TEST_SUITES will also run the 'dnf' test cases, so also check it to determine whether to create rpm index or not. This is to fix the following error when TEST_SUITES = "auto". RESULTS - dnf.DnfRepoTest.test_dnf_makecache - Testcase 1744: ERROR (From OE-Core rev: c1f4177848d25a9121f2a85da655ee414cd424b1) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

testimage.bbclass: fix behavior of empty TEST_SUITES

2018-06-04T14:15:00+00:00

The current behaviour of TEST_SUITES is very confusing. setting: TEST_SUITES = "" result: Execute all test cases. setting: TEST_SUITES = "some_case_not_exist" result: Error out with 'Empty test suite' message. The expected behaviour of TEST_SUITES should be: 1. when 'auto' is in it, execute as many test cases as possible 2. when no valid test case is specified, error out and give user message The first one is implemented by a previous patch. The second one is fixed in this patch. Also add debug message to show test cases to be executed. This is for easier debugging. (From OE-Core rev: 909568821fbad8a6a7034b10a2dc349a210fdfc6) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

meson.bbclass: refactor native override

2018-06-04T14:15:00+00:00

The native override is specified in two different places, so let's move it into a function to reduce code duplication. (From OE-Core rev: c455ec4a12d4966524da9436722476aa2d428765) Signed-off-by: Martin Kelly Signed-off-by: Richard Purdie