linux/poky.git/meta/classes/kernel-yocto.bbclass, branch uninative-2.2

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

kernel-yocto: check git config during checkout

2018-03-04T11:35:40+00:00

Initialize the git config prior creating a git repository in a plain directory. (From OE-Core rev: 0e3a9bed988b5fd4de770fe8cd1160b9f6c8c365) Signed-off-by: Justin Bronder Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

kernel-yocto: make SRC_URI defconfig removal more specific

2018-01-27T13:15:28+00:00

commit 7e98c295c1bb511e [kernel-yocto: ensure that only a single defconfig is processed] has an overly broad replacement strategy for 'defconfig' and hence will chop up any fragment name that happens to contain that string. If we change the processing to split on whitespace and drop any full work 'defconfig' fragments, we'll get the behaviour we want (no duplicate defconfigs, but fragments with defconfig in their name are fine). [YOCTO #12487] (From OE-Core rev: fd2678190db6575dc909104b60c284d0c41f605f) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kernel-yocto: ensure that only a single defconfig is processed

2017-12-10T22:45:21+00:00

As a follow up to the changes to ensure that KBUILD_DEFCONFIG will always get its defconfig into the processing, we also should ensure that we don't get both a KBUILD_DEFCONFIG and a SRC_URI defconfig in the configuration queue. If both are in the configuration queue, we end up with competing values and a potentially long running check of 5000+ options x 2 against the final .config. By removing the defconfig found from the SRC_URI when one is found via KBUILD_DEFCONFIG, we ensure that only one will be processed. (From OE-Core rev: 7e98c295c1bb511ece51b5f8c97f26c173ddaf76) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kernel-yocto: Stop the build if defconfig is missing

2017-12-10T22:45:21+00:00

The bberror does not stop the build correctly, this should be a bbfatal_log to ensure the failure correctly stops the build and logs the failure. Part of [YOCTO #12162] (From OE-Core rev: 44ff06635e7f575e67b7ebba5d6900b8ddbc4a06) Signed-off-by: Saul Wold Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kernel-yocto: ensure sccs variable is set when using KBUILD_DEFCONFIG

2017-12-10T22:45:21+00:00

When using KBUILD_DEFCONFIG, $sccs should be set to the $WORKDIR/defconfig regardless if it compares or is copied. Otherwise $sccs is not set and the defconfig is not found correctly. Part of [YOCTO #12162] (From OE-Core rev: b63cc051f1eb58c768f49db2c04843336e62d3df) Signed-off-by: Saul Wold Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kernel-yocto: relax BSP definition test

2017-08-24T12:48:10+00:00

commit 44aea7b873 [kernel-yocto: ensure that only valid BSPs are built] introduced a new check to ensure that a valid BSP definition was found, rather than building something that 'closely' matched the current MACHINE. This check breaks valid configurations which do not have a bsp definition but are otherwise completely configured machines. To allow both elements to co-exist (and not add warnings or errors to otherwise valid builds), we first check to see if an empty bsp definition was found, but then check to see if a defconfig was provided. If a defconfig has been provided, that is a sign that the board configuration is complete and we should continue the build without otherwise bothering the user. Tested on meta-raspberrypi and linux-yocto* (From OE-Core rev: 156cf9e25f875a50f907e570d9b62cbc2c051133) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kernel-yocto: fix typo in error message

2017-08-24T12:48:10+00:00

(From OE-Core rev: 92b4e043e9e2125105c697be2d0f75b3f01f91b1) Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie

kernel-yocto: ensure that only valid BSPs are built

2017-08-23T11:06:51+00:00

There was a bug in the search routines responsible for locating BSP definitions which returned a valid match if only the ktype matched. This meant that someone looking for "qemux86foo" (which is an invalid definition) would potentially end up building "qemuarm" and be none the wiser (until it didn't boot). With this fix to the tools search routine, and improved return code testing, we will now stop the build and report and error to the user. [YOCTO: #11878] (From OE-Core rev: 44aea7b87307795fe4e089c51d45afccaa2f6525) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kernel-yocto: propagate configuration errors to bbclass

2017-07-17T13:01:38+00:00

As pointed out by klapperichpaul@johndeere.com, missing configuration fragments were being picked up twice, once by the tools and once by the bbclass. Unfortunately, the tools error message was being detected as configs, and hence no error was reported at all. Rather than catching the output of the tools, we can instead check the return code and propagate the error message from the tools directly to the user. [YOCTO #11649] (From OE-Core rev: 960652416e2390337df6d9734375d6829ceb6420) Signed-off-by: Bruce Ashfield Signed-off-by: Ross Burton Signed-off-by: Richard Purdie