linux/poky.git/meta/classes-recipe, branch 5.0_M3

kernel-fitImage: only include valid compatible line

2024-03-08T08:06:16+00:00

Without this commit the configuration node includes the compatible line 'compatible = [00];' if EXTERNAL_KERNEL_DEVICETREE is not defined, i.e. if PREFERRED_PROVIDER_virtual/dtb is not used. This prevents u-boot from using this configuration and it prints the message "Could not find configuration node". An additional check also ensures that the written compatible line never contains an empty compatible. The functionality to add the compatible line was added in commit f4c82fb6da89 ("kernel-fitImage: add machine compatible to config section"). (From OE-Core rev: f8f3a52b2f924789552e6a3f889162ff07e0887f) Signed-off-by: Christian Taedcke Signed-off-by: Richard Purdie

go.bbclass: set GOPROXY

2024-03-08T08:06:16+00:00

The GOPROXY is already correctly defined on the native sys root and this can be checked using the bitbake devshell: | $ go env GOPROXY | https://proxy.golang.org,direct The go_do_compile task calls the compiler directly so the GOPROXY env is not seen because it's not defined in the shell. Defining it explicitly solves this problem and was to avoid setting it in the recipes itself. (From OE-Core rev: e0919a3f7bc26b1ea9fb57740de4a9a3b9253f26) Signed-off-by: Jose Quaresma Signed-off-by: Richard Purdie

oeqa/runtime/login: Various code improvements and fixes

2024-03-07T17:27:51+00:00

* Allow tools to be found from the host PATH so that imagemagick from a buildtools tarball/sdk can work * Reformat the code to have imports at the start of the file and have more standard formatting and whitespace * Always save copies of the images, the space imapct is negligle compared to the debug win * Write the images to ${T} * Use bb.utils.mkdirhier() instead of more complex code * Restrict the tests to images containing matchbox-desktop (From OE-Core rev: d09989b49517830297654e4d1d150aaa8723c41a) Signed-off-by: Richard Purdie

image_types.bbclass: fix vfat image names

2024-03-06T12:13:16+00:00

Remove the appended ${IMAGE_NAME_SUFFIX}, since it is already included in ${IMAGE_NAME}. In commit 26d97acc7137 ("image-artifact-names: include ${IMAGE_NAME_SUFFIX} directly in both ${IMAGE_NAME} and ${IMAGE_LINK_NAME}") ${IMAGE_NAME_SUFFIX} was included into ${IMAGE_NAME}. In this commit all other filesystems in image_types.bbclass were adapted. (From OE-Core rev: e3460853cdeae78762b31c6a846210f134bcd9ef) Signed-off-by: Christian Taedcke Signed-off-by: Richard Purdie

bmaptool: now part of Yocto Project

2024-03-05T12:24:50+00:00

The bmaptool (previously: bmap-tools, bmap-tool, bmaptool) has been moved to be under the Yocto Project umbrella and is now hosted at: github.com/yoctoproject/bmaptool [RP: Added a couple of missing renames] (From OE-Core rev: 7a036b1a1ec7dcd27dbe18d4c2e703bd2a8af182) Signed-off-by: Trevor Woerner Signed-off-by: Richard Purdie

goarch: disable dynamic linking globally

2024-03-03T16:28:20+00:00

With go-1.21 dynamic linking cause a runtime panic: | root@qemux86-64:~# go-helloworld | panic: runtime error: index out of range [0] with length 0 | | goroutine 1 [running]: | flag.init() | /usr/lib/go/src/flag/flag.go:1199 +0xf9 In my opinion, this would be a good trade-off so that we can update and leave the version 1.20 for the next LTS 5.0 since we are already quite behind on the version available upstream which already has the 1.22 available. (From OE-Core rev: 827c60b79e7fcafd14e68870f6b69dcc48ac9c39) Signed-off-by: Jose Quaresma Signed-off-by: Richard Purdie

u-boot: Move UBOOT_INITIAL_ENV back to u-boot.inc

2024-03-03T16:25:20+00:00

Commit cc6c3e31526d ("u-boot: Move definitions to common locations") moved UBOOT_INITIAL_ENV to uboot-config.bbclass, but it should be kept at u-boot.inc because it encodes ${PN} in it, which should be set by the U-Boot recipe. Currently, whatever inherits uboot-config bbclass will fill-in its own PN, which would change the content of UBOOT_INITIAL_ENV per-package. Cc: Klaus Heinrich Kiwi Cc: Marek Vasut Fixes: cc6c3e31526d ("u-boot: Move definitions to common locations") (From OE-Core rev: 0b0c4b37d318b86f100512476ffd861e0ce1f47e) Signed-off-by: Fabio Estevam Signed-off-by: Richard Purdie

waf: Improve version parsing to avoid failing on warnings

2024-03-01T09:31:10+00:00

waf uses an inline tar file extracted by the tarfile module. The tarfile module may print a warning when used with default 'filter' argument[0]. When called to get the version, the first time after unpack, the output may look like: # output from lower modules (e.g: warnings from tarfile, ...) waf X.Y.Z ... This patch makes the version parsing more precise by looking at the first line matching "waf ". [0]: https://docs.python.org/3.12/library/tarfile.html#extraction-filters (From OE-Core rev: 643b799a0c11d82907dd82991c19b003fe20a8b0) Signed-off-by: Yoann Congal Signed-off-by: Richard Purdie

libc-locale: fix ASCII compatible warning cause build failure.

2024-02-29T10:26:13+00:00

Some locales are not listed in glibc locales support list, but can be generated, here using ja_JP.SHIFT_JIS as an example. We can add following line into local.conf to enable and generate it: GLIBC_GENERATE_LOCALES += "en_GB.UTF-8 en_US.UTF-8 ja_JP.UTF-8 ja_JP.SHIFT_JIS" IMAGE_LINGUAS += "ja-jp en-us ja-jp.shift-jis" The localedef tool would report a warning and exit with 1, that cause build failure, error message as below: [warning] character map `SHIFT_JIS' is not ASCII compatible, locale not ISO C compliant [--no-warnings=ascii] So add a --no-warnings=ascii in libc-package.bbclass to fix build failure if someone needs those locale in yocto. (From OE-Core rev: 1048992c0d2a2bda3464185efdac5cc986a583d4) Signed-off-by: Xiangyu Chen Signed-off-by: Richard Purdie

testimage: create a list of failed test post actions

2024-02-27T11:35:43+00:00

testimage is able to detect whenever a test run leads to some tests failing, and execute some actions in this case. The only action currently defined in such case is to retrieve artifacts from the target under test, as listed in TESTIMAGE_FAILED_QA_ARTIFACTS In order to be able to add multiple actions, define a central function to gather all "post actions" to run whenever a test has failed (run_failed_tests_post_actions). This function contains a table listing all functions to be called whenever a test fails. Any function in this table will be provided with bitbake internal data dictionary ("d") and the current runtime testing context ("tc"). Isolate all this feature in a dedicated postactions.py file inherited by testimage. This patch does not bring any functional change. (From OE-Core rev: c01aa8df0613a103859b4431d3cc5056b2fef1b8) Signed-off-by: Alexis Lothoré Signed-off-by: Richard Purdie