linux/poky.git/meta/conf, branch yocto-5.0.9

yocto-uninative: Update to 4.7 for glibc 2.41

2025-04-07T13:34:44+00:00

(From OE-Core rev: 7626067432743657e9c536ca16a2dac513ba4929) Signed-off-by: Michael Halstead Signed-off-by: Richard Purdie Signed-off-by: Martin Jansa Signed-off-by: Steve Sakoman

ccache.conf: Add include_file_ctime to sloppiness

2025-03-05T14:03:47+00:00

When multiple recipes are built in parallel, Ccache sometimes refuses to lookup some objects in cache, leading to undesired cache misses. The root cause of this is an interaction between the way how bitbake constructs a recipe sysroot and Ccache's `include_file_ctime` check. Whenever bitbake creates a recipe's sysroot it hardlinks the files provided by a recipes dependencies. Adding a hardlink to a file changes it's ctime which in turn leads Ccache to believe that the file was modified thus aborting the cache lookup. To avoid this situation, add `include_file_ctime` to the list of checks that should be ignored using the Ccache sloppiness configuration option [1]. Example of a log entry that Ccache ignores a file: / |recipe-sysroot/usr/include/bits/pthread_stack_min.h had status change |near or after invocation (ctime 1739822508.107677255, invocation time |1739822507.970071107) \ 1 - https://ccache.dev/manual/4.10.2.html#config_sloppiness (From OE-Core rev: c74a6d6afc52606825e583cae1162e13a5369498) Signed-off-by: Fabio Berton Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie (cherry picked from commit 4899698297c7783e02aba5388e0469cc83bd2f70) Signed-off-by: Steve Sakoman

u-boot: kernel-fitimage: Fix dependency loop if UBOOT_SIGN_ENABLE and UBOOT_ENV enabled

2025-02-03T14:13:13+00:00

In case both UBOOT_SIGN_ENABLE and UBOOT_ENV are enabled and kernel-fitimage.bbclass is in use to generate signed kernel fitImage, there is a circular dependency between uboot-sign and kernel-fitimage bbclasses . The loop looks like this: kernel-fitimage.bbclass: - do_populate_sysroot depends on do_assemble_fitimage - do_assemble_fitimage depends on virtual/bootloader:do_populate_sysroot - virtual/bootloader:do_populate_sysroot depends on virtual/bootloader:do_install => The virtual/bootloader:do_install installs and the virtual/bootloader:do_populate_sysroot places into sysroot an U-Boot environment script embedded into kernel fitImage during do_assemble_fitimage run . uboot-sign.bbclass: - DEPENDS on KERNEL_PN, which is really virtual/kernel. More accurately - do_deploy depends on do_uboot_assemble_fitimage - do_install depends on do_uboot_assemble_fitimage - do_uboot_assemble_fitimage depends on virtual/kernel:do_populate_sysroot => do_install depends on virtual/kernel:do_populate_sysroot => virtual/bootloader:do_install depends on virtual/kernel:do_populate_sysroot virtual/kernel:do_populate_sysroot depends on virtual/bootloader:do_install Attempt to resolve the loop. Pull fitimage configuration options into separate new configuration file image-fitimage.conf so these configuration options can be shared by both uboot-sign.bbclass and kernel-fitimage.bbclass, and make use of mkimage -f auto-conf / mkimage -f auto option to insert /signature node key-* subnode into U-Boot control DT without depending on the layout of kernel fitImage itself. This is perfectly valid to do, because the U-Boot /signature node key-* subnodes 'required' property can contain either of two values, 'conf' or 'image' to authenticate either selected configuration or all of images when booting the fitImage. For details of the U-Boot fitImage signing process, see: https://docs.u-boot.org/en/latest/usage/fit/signature.html For details of mkimage -f auto-conf and -f auto, see: https://manpages.debian.org/experimental/u-boot-tools/mkimage.1.en.html#EXAMPLES (From OE-Core rev: 259bfa86f384206f0d0a96a5b84887186c5f689e) Fixes: 5e12dc911d0c ("u-boot: Rework signing to remove interdependencies") Reviewed-by: Adrian Freihofer (From OE-Core rev: d7bd9c6276611c8c8de0c2a24947783eae5d932a) Signed-off-by: Marek Vasut Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman

tune-cortexa32: set tune feature as armv8a

2024-11-26T14:11:30+00:00

Cortexa32 is a 32-bit armv8a architecture processor, so set the tune feature as armv8a instead of aarch64 which is 64-bit armv8a architecture. It solves the following build error while compiling libgcc-initial and libssp-nonshared. -- snip -- aarch64-poky-linux-musl-gcc: error: unrecognized command-line option '-mfpu=neon' aarch64-poky-linux-musl-gcc: error: unrecognized command-line option '-mfloat-abi=hard' -- snip -- (From OE-Core rev: a83ead146c15772970c7ca649e81929302349033) Signed-off-by: Jagadeesh Krishnanjanappa Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie (cherry picked from commit 3b898270aca62559dfa42ed71d296fe8a8b46a41) Signed-off-by: Steve Sakoman

bitbake.conf: Add truncate to HOSTTOOLS

2024-10-02T13:15:15+00:00

Some wic images need this command. Since it is part of coreutils, it doesn't really cost anything to have in HOSTTOOLS and it avoids signifiant build dependencies on coreutils-native. [YOCTO #15571] (From OE-Core rev: 85451cdaee4718233211da1e43db01f5cd2b1aff) Signed-off-by: Richard Purdie (cherry picked from commit 522000ce5c4f0201cbe42d7826b6a8489ed10117) Signed-off-by: Steve Sakoman

yocto-uninative: Update to 4.6 for glibc 2.40

2024-09-19T12:11:35+00:00

(From OE-Core rev: 0a8ba360f111d379af436de86e0a990be02910bb) Signed-off-by: Michael Halstead Signed-off-by: Richard Purdie (cherry picked from commit b29bfd333dffe635ab67475dcd8d22ad8b114c84) Signed-off-by: Steve Sakoman

maintainers.inc: add self for unassigned python recipes

2024-08-26T12:18:44+00:00

Add myself as maintainer for the following: - python3-setuptools - python3-smmap - python3-subunit - python3-testtools With that, every Python recipe in oe-core has a maintainer assigned. (From OE-Core rev: 97c2cf74e556511b3827362f6b3439daa26091e9) Signed-off-by: Trevor Gamblin Signed-off-by: Alexandre Belloni (cherry picked from commit f7c4ab54d3ff1895d9fcb9aa20dece5e0661579d) Signed-off-by: Steve Sakoman

maintainers.inc: update self e-mail address

2024-08-01T13:08:09+00:00

(From OE-Core rev: 54134c24e17f28223259eaaba41ff2e2ea5b55d6) Signed-off-by: Michael Opdenacker Signed-off-by: Richard Purdie (cherry picked from commit 0d4a435141c71710e479b7f49c38aba9f57cd1d7) Signed-off-by: Steve Sakoman

layer.conf: Add os-release to SIGGEN_EXCLUDERECIPES_ABISAFE

2024-07-26T14:43:46+00:00

This rebuilds whenever DISTRO_VERSION changes (i.e. any commit is made) and systemd depends upon it so lots of things end up rebuilding which isn't necessary, (From OE-Core rev: 9d2eded1d423a24a8fa811f26d501bd68cd7a1be) Signed-off-by: Richard Purdie Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 002a2a9d977ed5b86138333c567d25616d38c60b) Signed-off-by: Steve Sakoman

multilib.conf: remove appending to PKG_CONFIG_PATH

2024-07-23T13:05:47+00:00

* Since commit [a23c482cab allarch: only enable allarch when multilib is not used], allarch recipes will also be installed into ${MLPREFIX}recipe-sysroot, so this appending is not needed. * This appending also causes some QA errors. Eg: for lib32-php, the recipe will use 's@${RECIPE_SYSROOT}@@g' to remove host specific path, this appending makes not all the host specific path are matched. (From OE-Core rev: e88f159989cbf8080f0a8fb449c878f2a5747774) Signed-off-by: Changqing Li Signed-off-by: Richard Purdie (cherry picked from commit e6e6076f1956c711814c14d76194794d950e45f8) Signed-off-by: Steve Sakoman