Hi, Bruce, Would you mind taking a look at this? Have you seen any issues building latest kernel 5.12-rc for aarch64 and seeing host objcopy being used instead of cross compile one? Please let us

Can we also upgrade git to 2.31.1 as a follow up ?

checkout: fix bug that makes checkout follow symlinks in leading path Upstream-Status: Acepted [https://github.com/git/git/commit/684dd4c2b414bcf648505e74498a608f28de4592] CVE:

From: Lars Poeschel <poeschel@...> The functions for checking the C compiler version call the compiler with the --version argument and capture stdout and stderr to extract the version

Thanks! As subject says, the patch applies to both gatesgarth and dunfell. -Mikko

Derived from the similar kernel fitImage sign testcase, the U-Boot fitImage testcases exercises the following fitimage.FitImageTest scenarios: * test_uboot_fit_image - create unsigned U-Boot

Duplicate the variables governing u-boot signing so that we can have a different set of keys/parameters signing the SPL. Signed-off-by: Klaus Heinrich Kiwi <klaus@...> ---

Add the necessary infrastructure to create a U-boot proper fitimage, sign it (using the same keys as the kernel-fitimage), and put the public key in the SPL binary so that verified SPL boot can be

Move some definitions from u-boot.inc into uboot-config.bbclass and similarly from kernel-fitimage.bbclass into uboot-sign.bbclass, so that they can be useful when signing the U-boot proper fitimage,

This patch series aims at extending U-Boot's verified boot support to also include SPL. Presently, setting UBOOT_SIGN_ENABLE instructs the classes uboot-sign and kernel-fitimage to create and sign a

I plan to take it when it hits master. Steve

PROVIDES sets up a name which can be used as DEPENDS (ie a build time dependency) in other recipes. If PROVIDES contains more than one name, they all just become aliases for each other. Since

This cast was accidentally dropped in https://git.savannah.gnu.org/cgit/grub.git/commit/?id=2bf40e9e5be9808b17852e688eead87acff14420 Signed-off-by: Khem Raj <raj.khem@...> Cc: Alistair Francis

do we need this on dunfell too?

I am seeing some failures https://errors.yoctoproject.org/Errors/Details/574541/

<richard.purdie@...> wrote: If there's code in the upstream tar file etc which is not involved at all in the build of the one particular sub component you're interested in then this

I hadn't considered ${PN}-lic :(. We can't win. If we change LIC_FILES_CHKSUM we'll see complaints from people scanning the code that there are licenses present in WORKDIR that are not in

The easiest is the fact that the workers all share an NFS mount which is at BASE_SHAREDDIR in config.json. See also WEBPUBLISH_DIR and  WEBPUBLISH_URL. We use this to share the reproducible build

what should be easy questions about packagegroups, inspired by my running across some puzzling packagegroup recipes in my travels recently. (i'll start with examples out of oe-core). first, as with