parsec-service 1.1.0 fails to compile with latest tpm2-tss update in meta-security: | error: failed to run custom build command for `tss-esapi v7.1.0` | | Caused by: | process didn't exit successfully

I have a native tool (dotnet cli) that i use for configure/compile. It used to run fine in honister but im now having issues in kirkstone after recently upgrading. I can switch to a devshell and execu

Fixes: ERROR: Missing SRC_URI checksum, please add those to the recipe: SRC_URI[parsec-service-1.2.0.sha256sum] = "f58e7ba859c22cc1904dc8298b1a7d94ee1ba3b4d4808f28e4cc0c96ddb149c9" Needed to S dir too

From: Gowtham Suresh Kumar <gowtham.sureshkumar@...> Signed-off-by: Gowtham Suresh Kumar <gowtham.sureshkumar@...> --- meta-parsec/lib/oeqa/runtime/cases/parsec.py | 8 +++++--- 1 file changed, 5 inser

From: Gowtham Suresh Kumar <gowtham.sureshkumar@...> Signed-off-by: Gowtham Suresh Kumar <gowtham.sureshkumar@...> --- .../parsec-service/parsec-service-crates.inc | 460 ++++++++++++++++++ .../parsec-

Ignore. Found another build issus

Fixes: ERROR: Missing SRC_URI checksum, please add those to the recipe: SRC_URI[parsec-service-1.2.0.sha256sum] = "f58e7ba859c22cc1904dc8298b1a7d94ee1ba3b4d4808f28e4cc0c96ddb149c9" Signed-off-by: Armi

FIxes: ERROR: Missing SRC_URI checksum, please add those to the recipe: SRC_URI[parsec-tool-0.6.0.sha256sum] = "f51d5d7f0caca1c335324b52482fa5edbf6c9cfd2e6865e5cb22716d52dcb367" Needed to have the pac

https://stackoverflow.com/questions/71073386/reading-file-would-overwrite-reserved-memory-failed-to-load-hello-world-bin How to use LMB? ?

https://stackoverflow.com/questions/71073386/reading-file-would-overwrite-reserved-memory-failed-to-load-hello-world-bin Hi, I had this issue last year and I solved it via device tree. However, I used

Hi, Iam working on a dunfell version and using a custom u-boot, kernel etc. I need to add u-boot-fw-utils to my image and its well documented that the recipe is obsolete and is replaced by the libuboo

Hi Richard, Noted. We will proceed to test the rc2 build. Best regards, Jing Hui

From: Gowtham Suresh Kumar <gowtham.sureshkumar@...> The patches update parsec service to 1.2.0 and the parsec tool to 0.6.0 releases. The RSA OAEP OEQA tests for parsec pkcs11 backend is disabled. Go

I'm trying to remove a series of packages from my yocto build but what I've tried hasn't worked so far. This is what I have: ``` PACKAGE_EXCLUDE += "\ avahi \ apt \ apt-native \ cmake \ cmake-native \

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-4.2.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP

A build flagged for QA (yocto-4.2.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-4.2.rc1 Build hash information: bitbake: 46e1ea2e9a203992bb

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-ids/suricata/suricata-crates.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/recipes-ids/suricata/suricata-crates.inc b/recipes-ids/sur

Had to delete some wonky Cargo.toml files to get update_crates to work. Manually updated one crate to a newer version included by update_crates as it would not compile. Manually applied several crates

This causes my image build to fail. I even tried the hello-mod recipe. I am using kirkstone. >build/conf$ tail -1 local.conf >CORE_IMAGE_EXTRA_INSTALL = "imx-firmware kernel-module-hello-mod" >build/t

The PERLVERSION likely has the wrong value in the native context due to reasons discussed in openembedded-core[1]. The upstream suggestion was to avoid use of PERLVERSION and switch to the direct func