[yocto] M+ & H bugs with Milestone Movements WW10

All, YP M+ or high bugs which moved to a new milestone in WW10 are listed below: Priority Bug ID Short Description Changer Owner Was Became High 15428 postinstall failures with opkg in systemd enabled images randy.macl...@windriver.com

[yocto] Enhancements/Bugs closed WW10!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count randy.macl...@windriver.com 4 yoann.con...@smile.fr 2 ross.bur...@arm.com 1 Grand Total 7 Thanks, *Stephen K. Jolley* *Yocto Project Program Manager* (*Cell*:(208) 244-4460 *

[yocto] Current high bug count owners for Yocto Project 5.0

All, Below is the list of top 25 bug owners as of the end of WW10 who have open medium or higher bugs and enhancements against YP 5.0. There are 35 possible work days left until the final release candidates for YP 5.0 needs to be released. Who Count michael.opdenac...@bootlin.com 39

[yocto] [meta-lts-mixins][kirkstone/rust][PATCH 11/11] rust: Fix build failure re-appeared on riscv32

From: Khem Raj Refresh the rustix-0.38.19 patch to include FICLONE definition which fixes the build issue surfaced with rust 1.75 Signed-off-by: Khem Raj Signed-off-by: Richard Purdie Signed-off-by: Jose Quaresma --- .../files/rv32-cargo-rustix-0.38.19-fix.patch | 30 +++ 1

[yocto] [meta-lts-mixins][kirkstone/rust][PATCH 09/11] rust: Revert PGO to it's default

From: Yash Shinde The rust profiler PGO (Profile-guided Optimization) options was disabled as a part rustdoc reproducibility fix. https://git.yoctoproject.org/poky/commit/meta/recipes-devtools/rust?id=321aebfa281bd28e368c684ece57867f6bd0cbe7 But, other applications (such as to build chromium

[yocto] [meta-lts-mixins][kirkstone/rust][PATCH 10/11] rust: reproducibility issue fix with v1.75

From: Yash Shinde With 1.75 rust release, the '.rustc' section of shared object libs are embedded with absolute path names which is casuing reproducibiluty issues. This change will fix the path name format back to '/rust/$hash' as in earlier versions. Below are the links for detailed bug

[yocto] [meta-lts-mixins][kirkstone/rust][PATCH 06/11] rust: Re-write RPATHs in the copies llvm-config

From: Khem Raj Ensure that it can still access the native-sysroot for dependencies, use ORIGIN to indicate this relative its install location, this also helps in this not getting into the output of llvm-config which could otherwise provide incorrect library paths target rust recipe builds (

[yocto] [meta-lts-mixins][kirkstone/rust][PATCH 05/11] rust: Enable rust oe-selftest.

From: Yash Shinde * Enable rust oe-selftest. * Include the dependent patches for rust oe-selftest in meta/recipes-devtools/rust/rust-source.inc * Disable rust oe-selftest for mips32 target (Rust upstream has classified it into tier 3 target, for which the Rust project does not build or

[yocto] [meta-lts-mixins][kirkstone/rust][PATCH 04/11] rust: Fix assertion failure error on oe-selftest

From: Yash Shinde Fixes: thread 'main' panicked at 'assertion failed: `(left == right)` left: `x86_64-unknown-linux-gnu`, right: `x86_64-poky-linux-gnu`: Cannot obtain compiler for non-native build triple at stage 0', compile.rs:1474:13 Add correct target value for cross-compiled

[yocto] [meta-lts-mixins][kirkstone/rust][PATCH 03/11] rust: Enable RUSTC_BOOTSTRAP to use nightly features during rust oe-selftest.

From: Yash Shinde Fixes: error: the option `Z` is only accepted on the nightly compiler When rust.channel is set to either beta or stable, we can't use nightly features on bootstrap without RUSTC_BOOTSTRAP. Set RUSTC_BOOTSTRAP=1 to use nightly features on stable or beta. Signed-off-by: Yash

[yocto] [meta-lts-mixins][kirkstone/rust][PATCH 01/11] rust: Fetch cargo from rust-snapshot dir.

From: Yash Shinde Fixes: Exception: no cargo executable found at `${B}/rustc-1.74.1-src/build/x86_64-unknown-linux-gnu/stage0/bin/cargo` Fix the cargo binary path error on oe-selftest and path set to rust-snapshot dir. Patch sent to upstream-

[yocto] [meta-lts-mixins][kirkstone/rust][PATCH 02/11] rust: detect user-specified custom targets in compiletest

From: Yash Shinde Fixes: thread 'main' panicked at 'failed to gather the target spec for '-unknown-linux-gnu', synthetic_targets.rs:66:9 Detect and fetch custom target configurations when rustc is bootstrapped in rust oe-selftest. Signed-off-by: Yash Shinde Signed-off-by: Richard

[yocto] [meta-security][PATCH] arpwatch: install man8 dir

From: "Jeremy A. Puhlman" The install expects man8 directory to already exists. If not created the man page gets installed as "man8", which causes conflicts with other packages, that expect it to be a directory. 'arpsnmp' ->

[yocto] Task Dependancies

Okay, In details There are base-initramfs.bb, image-ext4.inc, image-ext4-debug.bb files and dm-verity file which depends upon the base-initramfs as we know that base-initramfs loads the actual rootfs so in image-ext4.inc i wrote a custom-task "do_simlink_ext4" inside which i just wrote

Re: [yocto] Task dependencies

Can you publish the layer somewhere? It's hard to tell what is going on, but perhaps you could check which task creates which artefacts in deploy directory, and consult the bitbake manual about task dependencies so they can be run in correct order. Alex On Thu, 7 Mar 2024 at 11:13, Bratiranjan

[linux-yocto][linux-yocto v5.15] kernel code for marvell cn96xx

Hi Bruce, Please help to merge this patch into our linux-yocto repo. repo: linux-yocto branch: v5.15/standard/cn-sdkv5.15/octeon v5.15/standard/preempt-rt/cn-sdkv5.15/octeon Thanks, Ruiqiang -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to

[linux-yocto] [PATCH] arm_mpam: replace acpi_table_mpam_msc with acpi_mpam_msc_node

From: Ruiqiang Hao When the ACPI_MPAM option is not enabled, there will be a warning during compilation. Replace acpi_table_mpam_msc with acpi_mpam_msc_node to fix this. In file included from drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c:14: include/linux/arm_mpam.h:33:52: warning: 'struct

Re: [yocto] Cannot ssh into qemu guest

I'd suggest that in the serial console you get: 1) check the ip address of the booted target 2) Run 'ssh root@localhost' on that target to check if login onto itself is OK 3) If you can ssh locally and the ip is 192.168.7.2, and you still have problem with 'ssh root@192.168.7.2', maybe you need