Re: [yocto] Unable to run arm 64 binary on arm64 machine

2023-11-14 Thread MOHAMMED HASSAN 
root@se-704a0efe85c4:~# ./hello
-sh: ./hello: No such file or directory
root@se-704a0efe85c4:~#

This is the response.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61692): https://lists.yoctoproject.org/g/yocto/message/61692
Mute This Topic: https://lists.yoctoproject.org/mt/102600996/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Unable to run arm 64 binary on arm64 machine

2023-11-14 Thread MOHAMMED HASSAN 
On Tue, Nov 14, 2023 at 11:40 PM, Khem Raj wrote:

> 
> it seems you have a mixed mode image where kernel is 64bit but userspace
> is 32bit, so you have to compile your app to be 32bit as well.
> otherwise you need to include 64bit runtime as well to support 64bit apps.
> 
> 

Unfortunately I don't have much clarity on how to achieve this. Can you suggest 
what i should do.
Thanks

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61690): https://lists.yoctoproject.org/g/yocto/message/61690
Mute This Topic: https://lists.yoctoproject.org/mt/102600996/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Architecture did not match

2023-11-14 Thread Khem Raj 
in your recipe, you need to add runtime dependencies. e.g.

RDEPENDS:${PN} += "bash"

or you can ignore the deps if your image has them all in already.
since your package is binary only.
add
INSANE_SKIP:${PN} = "file-rdeps"

On Tue, Nov 14, 2023 at 11:29 PM MOHAMMED HASSAN
 wrote:
>
> On Tue, Nov 14, 2023 at 11:17 PM, Khem Raj wrote:
>
> add lib32-testing-firmware in your image instead of testing-firmware
>
> NOTE: lib32-gst-plugin-video-sink: compiling from external source tree 
> /Yocto_sdk/yocto_sdk/aml-comp/multimedia/gst-plugin-video-sink
> NOTE: lib32-gst-plugin-aml-v4l2dec: compiling from external source tree 
> /Yocto_sdk/yocto_sdk/aml-comp/multimedia/gst-plugin-aml-v4l2dec
> NOTE: u-boot: compiling from external source tree 
> /Yocto_sdk/yocto_sdk/aml-comp/uboot
> ERROR: lib32-testing-firmware-0.1-r0 do_package_qa: QA Issue: Architecture 
> did not match (x86-64, expected ARM) on 
> /work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/packages-split/lib32-testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/linux-x64/node.napi.musl.node
> Architecture did not match (x86-64, expected ARM) on 
> /work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/packages-split/lib32-testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/linux-x64/node.napi.glibc.node
> Architecture did not match (AArch64, expected ARM) on 
> /work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/packages-split/lib32-testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/android-arm64/node.napi.armv8.node
> Architecture did not match (AArch64, expected ARM) on 
> /work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/packages-split/lib32-testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/linux-arm64/node.napi.armv8.node
>  [arch]
> WARNING: lib32-testing-firmware-0.1-r0 do_package_qa: QA Issue: 
> /home/root/Edge/install.sh contained in package lib32-testing-firmware 
> requires /bin/bash, but no providers found in 
> RDEPENDS_lib32-testing-firmware? [file-rdeps]
> ERROR: lib32-testing-firmware-0.1-r0 do_package_qa: QA run found fatal 
> errors. Please consider fixing them.
> ERROR: Logfile of failure stored in: 
> /Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/temp/log.do_package_qa.52476
> ERROR: Task 
> (virtual:multilib:lib32:/Yocto_sdk/yocto_sdk/meta-blaze/recipes-example/testing-firmware/testing-firmware_0.1.bb:do_package_qa)
>  failed with exit code '1'
> NOTE: Tasks Summary: Attempted 7801 tasks of which 7737 didn't need to be 
> rerun and 1 failed.
> NOTE: Writing buildhistory
> NOTE: Writing buildhistory took: 1 seconds
>
> Summary: 1 task failed:
>
> Still the same error but now the architecture is shown different.
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61689): https://lists.yoctoproject.org/g/yocto/message/61689
Mute This Topic: https://lists.yoctoproject.org/mt/102600630/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Architecture did not match

2023-11-14 Thread MOHAMMED HASSAN 
On Tue, Nov 14, 2023 at 11:17 PM, Khem Raj wrote:

> 
> add lib32-testing-firmware in your image instead of testing-firmware
> 
> 

NOTE: lib32-gst-plugin-video-sink: compiling from external source tree 
/Yocto_sdk/yocto_sdk/aml-comp/multimedia/gst-plugin-video-sink
NOTE: lib32-gst-plugin-aml-v4l2dec: compiling from external source tree 
/Yocto_sdk/yocto_sdk/aml-comp/multimedia/gst-plugin-aml-v4l2dec
NOTE: u-boot: compiling from external source tree 
/Yocto_sdk/yocto_sdk/aml-comp/uboot
ERROR: lib32-testing-firmware-0.1-r0 do_package_qa: QA Issue: Architecture did 
not match (x86-64, expected ARM) on 
/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/packages-split/lib32-testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/linux-x64/node.napi.musl.node
Architecture did not match (x86-64, expected ARM) on 
/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/packages-split/lib32-testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/linux-x64/node.napi.glibc.node
Architecture did not match (AArch64, expected ARM) on 
/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/packages-split/lib32-testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/android-arm64/node.napi.armv8.node
Architecture did not match (AArch64, expected ARM) on 
/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/packages-split/lib32-testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/linux-arm64/node.napi.armv8.node
 [arch]
WARNING: lib32-testing-firmware-0.1-r0 do_package_qa: QA Issue: 
/home/root/Edge/install.sh contained in package lib32-testing-firmware requires 
/bin/bash, but no providers found in RDEPENDS_lib32-testing-firmware? 
[file-rdeps]
ERROR: lib32-testing-firmware-0.1-r0 do_package_qa: QA run found fatal errors. 
Please consider fixing them.
ERROR: Logfile of failure stored in: 
/Yocto_sdk/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-testing-firmware/0.1-r0/temp/log.do_package_qa.52476
ERROR: Task 
(virtual:multilib:lib32:/Yocto_sdk/yocto_sdk/meta-blaze/recipes-example/testing-firmware/testing-firmware_0.1.bb:do_package_qa)
 failed with exit code '1'
NOTE: Tasks Summary: Attempted 7801 tasks of which 7737 didn't need to be rerun 
and 1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds

Summary: 1 task failed:

Still the same error but now the architecture is shown different.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61687): https://lists.yoctoproject.org/g/yocto/message/61687
Mute This Topic: https://lists.yoctoproject.org/mt/102600630/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Architecture did not match

2023-11-14 Thread Khem Raj 
add lib32-testing-firmware in your image instead of testing-firmware

On Tue, Nov 14, 2023 at 10:26 PM MOHAMMED HASSAN
 wrote:
>
> Hi guys,
> So the SDK my vendor provided kernel toolchain of "aarch64-poky-linux-gcc" 
> while the application uses a 32 bit toolchain 
> "arm-pokymllib32-linux-gnueabi-gcc".
> So i want to just copy my nodejs application to the home directory. To 
> compensate for the architecture issues I have made the changes in my recipe 
> file as shown below.
>
> testing-firmware_0.1.bb:
> DESCRIPTION =  "Testing firmware for Edge 3 hubs"
>
> LICENSE = "MIT"
> LIC_FILES_CHKSUM = 
> "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
>
> SRC_URI = "file://Edge_3_firmware_testing.zip"
>
> S = "${WORKDIR}"
> INSANE_SKIP:${PN} += "arch:/Edge/node_modules/"
>
> do_install() {
> install -d ${D}/home/root
> cp -r ${WORKDIR}/Edge -d ${D}/home/root/
> cp -r ${WORKDIR}/Edge -d ${D}{bindir}/
> }
>
> FILES_${PN} = "/home/root/Edge"
>
> But when i try to build the testing firmware I get the following error:
>
> ERROR: testing-firmware-0.1-r0 do_package_qa: QA Issue: Architecture did not 
> match (ARM, expected AArch64) on 
> /work/aarch64-poky-linux/testing-firmware/0.1-r0/packages-split/testing-firmware-dbg/home/root/Edge/node_modules/epoll/build/Release/.debug/epoll.node
> Architecture did not match (ARM, expected AArch64) on 
> /work/aarch64-poky-linux/testing-firmware/0.1-r0/packages-split/testing-firmware-dbg/home/root/Edge/node_modules/epoll/build/Release/obj.target/.debug/epoll.node
>  [arch]
> ERROR: testing-firmware-0.1-r0 do_package_qa: QA Issue: Architecture did not 
> match (ARM, expected AArch64) on 
> /work/aarch64-poky-linux/testing-firmware/0.1-r0/packages-split/testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/android-arm/node.napi.armv7.node
> Architecture did not match (x86-64, expected AArch64) on 
> /work/aarch64-poky-linux/testing-firmware/0.1-r0/packages-split/testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/linux-x64/node.napi.musl.node
> Architecture did not match (x86-64, expected AArch64) on 
> /work/aarch64-poky-linux/testing-firmware/0.1-r0/packages-split/testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/linux-x64/node.napi.glibc.node
> Architecture did not match (ARM, expected AArch64) on 
> /work/aarch64-poky-linux/testing-firmware/0.1-r0/packages-split/testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/linux-arm/node.napi.armv7.node
> Architecture did not match (ARM, expected AArch64) on 
> /work/aarch64-poky-linux/testing-firmware/0.1-r0/packages-split/testing-firmware/home/root/Edge/node_modules/@serialport/bindings-cpp/prebuilds/linux-arm/node.napi.armv6.node
> Architecture did not match (ARM, expected AArch64) on 
> /work/aarch64-poky-linux/testing-firmware/0.1-r0/packages-split/testing-firmware/home/root/Edge/node_modules/epoll/build/Release/epoll.node
> Architecture did not match (ARM, expected AArch64) on 
> /work/aarch64-poky-linux/testing-firmware/0.1-r0/packages-split/testing-firmware/home/root/Edge/node_modules/epoll/build/Release/obj.target/epoll.node
> Architecture did not match (ARM, expected AArch64) on 
> /work/aarch64-poky-linux/testing-firmware/0.1-r0/packages-split/testing-firmware/home/root/Edge/node_modules/epoll/build/Release/obj.target/epoll/src/epoll.o
>  [arch]
> WARNING: testing-firmware-0.1-r0 do_package_qa: QA Issue: 
> /home/root/Edge/node_modules/epoll/build/Release/obj.target/epoll.node 
> contained in package testing-firmware requires libpthread.so.0(GLIBC_2.4), 
> but no providers found in RDEPENDS_testing-firmware? [file-rdeps]
> WARNING: testing-firmware-0.1-r0 do_package_qa: QA Issue: 
> /home/root/Edge/node_modules/epoll/build/Release/obj.target/epoll.node 
> contained in package testing-firmware requires libc.so.6(GLIBC_2.9), but no 
> providers found in RDEPENDS_testing-firmware? [file-rdeps]
> WARNING: testing-firmware-0.1-r0 do_package_qa: QA Issue: 
> /home/root/Edge/node_modules/epoll/build/Release/obj.target/epoll.node 
> contained in package testing-firmware requires libc.so.6(GLIBC_2.4), but no 
> providers found in RDEPENDS_testing-firmware? [file-rdeps]
> WARNING: testing-firmware-0.1-r0 do_package_qa: QA Issue: 
> /home/root/Edge/node_modules/epoll/build/Release/obj.target/epoll.node 
> contained in package testing-firmware requires libstdc++.so.6(CXXABI_1.3.9), 
> but no providers found in RDEPENDS_testing-firmware? [file-rdeps]
> WARNING: testing-firmware-0.1-r0 do_package_qa: QA Issue: 
> /home/root/Edge/node_modules/epoll/build/Release/obj.target/epoll.node 
> contained in package testing-firmware requires 
> libstdc++.so.6(CXXABI_ARM_1.3.3), but no providers found in 
> RDEPENDS_testing-firmware? [file-rdeps]
> WARNING: testing-firmware-0.1-r0 do_package_qa: QA Issue: 
> /home/root/Edge/node_modules/epoll/build/Release/obj.target/epoll.node 
> contained

[linux-yocto][v6.1/standard/sdkv5.10/axxia && v6.1/standard/preempt-rt/sdkv5.10/axxia][PATCH 1/1] ARM: dts: axxia: fix leading 0x and 0s warning

2023-11-14 Thread LiweiSong via lists.yoctoproject.org 
Improve the DTS files by removing all the leading "0x" and "0s" to fix
the following types of dtc warnings:

arch/arm/boot/dts/axm55xx.dtsi:87.24-92.4: Warning (unit_address_format): 
/ccn@0x20: unit name should not have leading "0x"
arch/arm/boot/dts/axm55xx.dtsi:99.20-105.4: Warning (unit_address_format): 
/sm0@0022: unit name should not have leading 0s

Signed-off-by: Liwei Song 
---
 arch/arm/boot/dts/axm5516-amarillo.dts |  2 +-
 arch/arm/boot/dts/axm55xx.dtsi | 10 +-
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/arch/arm/boot/dts/axm5516-amarillo.dts 
b/arch/arm/boot/dts/axm5516-amarillo.dts
index 8572efaace2c..5bbab36c0532 100644
--- a/arch/arm/boot/dts/axm5516-amarillo.dts
+++ b/arch/arm/boot/dts/axm5516-amarillo.dts
@@ -33,7 +33,7 @@  {
axxia,mdio-clk-period = <0xf0>;
max-speed = <10>;
 
-   phy0: ethernet-phy@0x1e {
+   phy0: ethernet-phy@1e {
reg = <0x1e>;
};
 };
diff --git a/arch/arm/boot/dts/axm55xx.dtsi b/arch/arm/boot/dts/axm55xx.dtsi
index b56b6cc9d45a..45761ff508ab 100644
--- a/arch/arm/boot/dts/axm55xx.dtsi
+++ b/arch/arm/boot/dts/axm55xx.dtsi
@@ -65,7 +65,7 @@ timer {
 <1 10 0xf08>;
};
 
-   edac: edac0@0x1000 {
+   edac: edac0@1000 {
compatible = "axxia,edac";
reg = <0 0x0022 0 0x1000>,
<0 0x000f 0 0x1000>,
@@ -84,7 +84,7 @@ edac: edac0@0x1000 {
status = "disabled";
};
 
-   ccn: ccn@0x20 {
+   ccn: ccn@20 {
compatible = "arm,ccn-504";
reg = <0x20 0x 0 0x100>;
interrupts = <0 181 4>;
@@ -96,7 +96,7 @@ perf_platform: perf_platform {
status = "disabled";
};
 
-   sm0: sm0@0022 {
+   sm0: sm0@22 {
compatible = "axxia,smmon";
reg = <0 0x0022 0 0x1000>,
<0x20 0x1003 0 0001000>;
@@ -104,7 +104,7 @@ sm0: sm0@0022 {
status = "disabled";
};
 
-   sm1: sm1@0022 {
+   sm1: sm1@22 {
compatible = "axxia,smmon";
reg = <0 0x000f 0 0x1000>,
<0x20 0x1003 0 0001000>;
@@ -112,7 +112,7 @@ sm1: sm1@0022 {
status = "disabled";
};
 
-   femac: femac@0x201012 {
+   femac: femac@201012 {
compatible = "axxia,acp-femac";
device_type = "network";
reg = <0x20 0x1012 0 0x1000>,
-- 
2.35.5


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13286): 
https://lists.yoctoproject.org/g/linux-yocto/message/13286
Mute This Topic: https://lists.yoctoproject.org/mt/102600907/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [yocto-autobuilder-helper][PATCH] config.json: temporarily disable pressure regulation for master-next ONLY

2023-11-14 Thread Randy MacLeod via lists.yoctoproject.org 
From: Randy MacLeod 

Builds and oe-selftest runs have been seen to take around 16 hours.
Temporarily disable pressure regulation in master-next ONLY
to see if the pressure regulation is a significant part of what's
causing the slow down.

Signed-off-by: Randy MacLeod 
---
 config.json | 2 --
 1 file changed, 2 deletions(-)

diff --git a/config.json b/config.json
index 0c581d1..ffe216b 100644
--- a/config.json
+++ b/config.json
@@ -50,8 +50,6 @@
 "BB_NUMBER_THREADS = '16'",
 "BB_NUMBER_PARSE_THREADS = '16'",
 "PARALLEL_MAKE = '-j 16 -l 52'",
-"BB_PRESSURE_MAX_CPU = '1'",
-"BB_PRESSURE_MAX_IO = '1'",
 "XZ_MEMLIMIT = '5%'",
 "XZ_THREADS = '8'",
 "ZSTD_THREADS = '8'",
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61683): https://lists.yoctoproject.org/g/yocto/message/61683
Mute This Topic: https://lists.yoctoproject.org/mt/102587267/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [yocto-autobuilder-helper][PATCH] patchtest: add selftest runner

2023-11-14 Thread Trevor Gamblin 
Add a runner that installs the patchtest dependencies in a Python venv
and then starts patchtest's selftests.

Signed-off-by: Trevor Gamblin 
---
 config.json|  7 +++
 scripts/run-patchtest-selftest | 18 ++
 2 files changed, 25 insertions(+)
 create mode 100755 scripts/run-patchtest-selftest

diff --git a/config.json b/config.json
index 0c581d1..e049a95 100644
--- a/config.json
+++ b/config.json
@@ -1676,6 +1676,13 @@
 "BBTARGETS" : "core-image-patchtest"
 }
 },
+   "patchtest-selftest" : {
+   "NEEDREPOS" : ["poky"],
+   "EXTRACMDS" : ["${SCRIPTSDIR}/run-patchtest-selftest 
${HELPERBUILDDIR}/.."],
+   "ADDLAYER" : [
+   "${BUILDDIR}/../meta-selftest"
+   ]
+   },
 "toaster" : {
 "EXTRACMDS" : ["${SCRIPTSDIR}/run-toaster-tests ${HELPERBUILDDIR} 
${HELPERBUILDDIR}/.."]
 }
diff --git a/scripts/run-patchtest-selftest b/scripts/run-patchtest-selftest
new file mode 100755
index 000..58edb0e
--- /dev/null
+++ b/scripts/run-patchtest-selftest
@@ -0,0 +1,18 @@
+#!/bin/bash
+#
+# SPDX-License-Identifier: GPL-2.0-only
+#
+# Called with $1 as the path to poky
+
+set -e
+set -u
+set -o pipefail
+set -x
+
+pokydir=$(realpath "$1")
+
+python3 -m venv venv --without-pip --system-site-packages
+source venv/bin/activate
+python3 -m pip install -r $pokydir/meta/lib/patchtest/requirements.txt
+
+$pokydir/meta/lib/patchtest/selftest/selftest
-- 
2.41.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61682): https://lists.yoctoproject.org/g/yocto/message/61682
Mute This Topic: https://lists.yoctoproject.org/mt/102586397/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [yocto-autobuilder2] config.py: add fedora38 to workers_prev_releases for dunfell

2023-11-14 Thread Steve Sakoman 
Signed-off-by: Steve Sakoman 
---
 config.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.py b/config.py
index 316109b..721f637 100644
--- a/config.py
+++ b/config.py
@@ -180,7 +180,7 @@ workers_prev_releases = {
 "honister" : ("alma8", "centos7", "centos8", "debian8", "debian9", 
"debian10", "debian11", "fedora29", "fedora30", "fedora31", "fedora32", 
"fedora33", "fedora34", "fedora35", "opensuse150", "opensuse151", 
"opensuse152", "opensuse153", "ubuntu1604", "ubuntu1804", "ubuntu1904", 
"ubuntu2004", "ubuntu2110", "ubuntu2204", "perf-"),
 "hardknott" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"debian11", "fedora31", "fedora32", "fedora33", "fedora34", "opensuse152", 
"ubuntu1604", "ubuntu1804", "ubuntu2004", "perf-"),
 "gatesgarth" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"fedora30", "fedora31", "fedora32", "opensuse150", "opensuse151", 
"opensuse152", "ubuntu1604", "ubuntu1804", "ubuntu1904", "ubuntu2004", "perf-"),
-"dunfell" : ("alma8", "centos7", "centos8", "debian8", "debian9", 
"debian10", "debian11", "fedora29", "fedora30", "fedora31", "fedora32", 
"fedora33", "fedora34", "fedora35", "fedora36", "fedora37", "opensuse150", 
"opensuse151", "opensuse152", "opensuse153", "ubuntu1604", "ubuntu1804", 
"ubuntu1904", "ubuntu2004", "ubuntu2204", "perf-"),
+"dunfell" : ("alma8", "centos7", "centos8", "debian8", "debian9", 
"debian10", "debian11", "fedora29", "fedora30", "fedora31", "fedora32", 
"fedora33", "fedora34", "fedora35", "fedora36", "fedora37", "fedora38", 
"opensuse150", "opensuse151", "opensuse152", "opensuse153", "ubuntu1604", 
"ubuntu1804", "ubuntu1904", "ubuntu2004", "ubuntu2204", "perf-"),
 "zeus" : ("centos7", "debian8", "debian9", "debian10", "fedora28", 
"fedora29", "fedora30", "opensuse150", "opensuse151", "ubuntu1604", 
"ubuntu1804", "ubuntu1904", "perf-"),
 "warrior" : ("centos7", "debian8", "debian9", "debian10", "fedora28", 
"fedora29", "fedora30", "opensuse150", "opensuse151", "ubuntu1604", 
"ubuntu1804", "ubuntu1904", "perf-"),
 "thud" : ("centos7", "debian8", "debian9", "debian10", "fedora28", 
"fedora29", "fedora30", "opensuse150", "opensuse151", "ubuntu1604", 
"ubuntu1804", "ubuntu1904", "perf-"),
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61681): https://lists.yoctoproject.org/g/yocto/message/61681
Mute This Topic: https://lists.yoctoproject.org/mt/102585525/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.2.4.rc3)

2023-11-14 Thread Jing Hui Tham 
Hi all,
 
Intel and WR YP QA is planning for QA execution for YP build yocto-4.2.4.rc3. 
We are planning to execute following tests for this cycle:
 
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
 
Runtime auto test for following platforms:
1. MinnowBoard Turbot - 32bit
2. Kaby Lake (7th Generation Intel(r) Core(tm) Processors)
3. Tiger Lake (11th Generation Intel(r) Core(tm) Processors)
4. Alder Lake-S (12th Generation Intel(r) Core(tm) Processors)
5. Raptor Lake-P (13th Generation Intel(r) Core(tm) Processors)
6. Edgerouter
7. Beaglebone

 
ETA for completion next Monday, 20 November 2023.
 
Best regards,
Jing Hui


> -Original Message-
> From: qa-build-notificat...@lists.yoctoproject.org  notificat...@lists.yoctoproject.org> On Behalf Of Pokybuild User
> Sent: Tuesday, November 14, 2023 3:04 PM
> To: yocto@lists.yoctoproject.org
> Cc: qa-build-notificat...@lists.yoctoproject.org
> Subject: [qa-build-notification] QA notification for completed autobuilder
> build (yocto-4.2.4.rc3)
> 
> 
> A build flagged for QA (yocto-4.2.4.rc3) was completed on the autobuilder
> and is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-4.2.4.rc3
> 
> 
> Build URL:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6188
> 
> Build hash information:
> 
> bitbake: c7e094ec3beccef0bbbf67c100147c449d9c6836
> meta-agl: bf791cba6a3bc53864bf719dc913cea352146f75
> meta-arm: 9bcc166bd5bb717aa86bb0464621a36abc51fa19
> meta-aws: b288fb9d29f67af79de07f039429fcf921e2abd3
> meta-intel: 0ed9b8ed17878274b80dbf713f50aa253dcd
> meta-mingw: d87d4f00b9c6068fff03929a4b0f231a942d3873
> meta-openembedded: 39968837196cb48209b71e8852dd04a2f8ccdca8
> meta-virtualization: b8db7002764712f2902fe9dea098c171b1128076
> oecore: 23b5141400b2c676c806df3308f023f7c04e34e0
> poky: 7235399a86b134e57d5eb783d7f1f57ca0439ae5
> 
> 
> 
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.pur...@linuxfoundation.org
> 
> 
> 
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61680): https://lists.yoctoproject.org/g/yocto/message/61680
Mute This Topic: https://lists.yoctoproject.org/mt/102582356/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Status 14 November 2023 (WW46)

2023-11-14 Thread Neal Caidin 
Current Dev Position: YP 5.0 M1

Next Deadline: 4th December 2023 YP 5.0 M1 build

Next Team Meetings:

   -

   Bug Triage meeting Thursday November 16, 7:30 am PDT (
   https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
   -

   Weekly Project Engineering Sync Tuesday November 14th at 8 am PDT (
   https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
   
   -

   Twitch -  See https://www.twitch.tv/theyoctojester


Key Status/Updates:

   -

   YP 4.3 was released, thanks to everyone who contributed!
   -

   YP 4.0.14 is out of QA and due for release
   -

   YP 3.1.29 is out of QA and due for release after investigation of vim
   reproducibility issues
   -

  YP 4.2.4 is currently being built
  -

   bitbake’s hash equivalence server has undergoing a lot of development
   (thanks Joshua!) including:
   -

  websockets support
  -

  user authentication/permissions support
  -

  entry removal API addition
  -

  support for multiple database backends
  -

   master saw various upgrades for the kernel and other components
   -

   the length of time rebuilds are taking on the autobuilder is a concern,
   world can take 16 hours as can oe-selftest with a cold sstate cache


Ways to contribute:

   -

   As people are likely aware, the project has a number of components which
   are either unmaintained, or have people with little to no time trying to
   keep them alive. These components include: patchtest, layerindex, devtool,
   toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many
   have open bugs. Help is welcome in trying to better look after these
   components!
   -

   There are bugs identified as possible for newcomers to the project:
   https://wiki.yoctoproject.org/wiki/Newcomers
   -

   There are bugs that are currently unassigned for YP 4.3. See:
   
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.3_Unassigned_Enhancements.2FBugs
   -

   We’d welcome new maintainers for recipes in OE-Core. Please see the list
   at:
   
http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc
   and discuss with the existing maintainer, or ask on the OE-Core mailing
   list. We will likely move a chunk of these to “Unassigned” soon to help
   facilitate this.
   -

   Help is very much welcome in trying to resolve our autobuilder
   intermittent issues. You can see the list of failures we’re continuing to
   see by searching for the “AB-INT” tag in bugzilla:
   https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT.
   -

   Help us resolve CVE issues: CVE metrics
   
   -

   We have a growing number of bugs in bugzilla, any help with them is
   appreciated.


YP 5.0 Milestone Dates:

   -

   YP 5.0 M1 build date 2023/12/04
   -

   YP 5.0 M1 Release date 2023/12/15
   -

   YP 5.0 M2 build date  2024/01/15
   -

   YP 5.0 M2 Release date 2024/01/24
   -

   YP 5.0 M3 build date  2024/02/19
   -

   YP 5.0 M3 Release date 2024/03/01
   -

   YP 5.0 M4 build date  2024/04/01
   -

   YP 5.0 M4 Release date 2024/04/30


Upcoming dot releases:

   -

   YP 3.1.29 build date 2023/10/30
   -

   YP 3.1.29 Release date 2023/11/10
   -

   YP 4.0.14 build date 2023/11/06
   -

   YP 4.0.14 Release date 2023/11/17
   -

   YP 4.2.4 build date 2023/11/13
   -

   YP 4.2.4 Release date 2023/11/24
   -

   YP 4.3.1 build date 2023/11/27
   -

   YP 4.3.1 Release date 2023/12/08
   -

   YP 3.1.30 build date 2023/12/11
   -

   YP 3.1.30 Release date 2023/12/22
   -

   YP 4.0.15 build date 2023/12/18
   -

   YP 4.0.15 Release date 2023/12/29
   -

   YP 4.3.2 build date 2024/01/08
   -

   YP 4.3.2 Release date 2024/01/19
   -

   YP 3.1.31 build date 2024/01/22
   -

   YP 3.1.31 Release date 2024/02/02
   -

   YP 4.0.16 build date 2024/01/29
   -

   YP 4.0.16 Release date 2024/02/09
   -

   YP 4.3.3 build date 2024/02/12
   -

   YP 4.3.3 Release date 2024/02/23
   -

   YP 3.1.32 build date 2024/03/04
   -

   YP 3.1.32 Release date 2024/03/15
   -

   YP 4.0.17 build date 2024/03/11
   -

   YP 4.0.17 Release date 2024/03/22
   -

   YP 4.3.4 build date 2024/03/25
   -

   YP 4.3.4 Release date 2024/04/05
   -

   YP 3.1.33 build date 2024/04/15
   -

   YP 3.1.33 Release date 2024/04/26
   -

   YP 4.0.18 build date 2024/04/22
   -

   YP 4.0.18 Release date 2024/05/03
   -

   YP 4.0.19 build date 2024/06/03
   -

   YP 4.0.19 Release date 2024/06/14


Tracking Metrics:

   -

   WDD 2533 (last week 2540) (
   https://wiki.yoctoproject.org/charts/combo.html)
   -

   OE-Core/Poky Patch Metrics
   -

  Total patches found: 1177 (last week 1173)
  -

  Patches in the Pending State: 253 (21%) [last week 253 (22%)]
  -

   https://autobuilder.yocto.io/pub/non-release/patchmetrics/


The Yocto Project’s technical governance is through its Technical Steering
Committee,

Re: [yocto] [RFC] devtool: support multiple sources

2023-11-14 Thread Alexander Kanavin 
I think no one actually anticipated all these corner cases when
devtool was written. In general it's simply not designed to handle
multiple sources in SRC_URI, it can do (tarball or git)+patches, and
not any of the other options. No one is expecting a fix for all of
them, perhaps it's best to keep the scope to plain gitsm://.

I don't have specific advice for the broader issue; if you have ideas,
it would be good to at least document them.

Alex

On Fri, 10 Nov 2023 at 17:24, Julien Stephan  wrote:
>
> Hi all,
>
> Sorry for the long message here, but I would really appreciate
> feedback from the community :)
>
> I am currently working on bug #14141
> (https://bugzilla.yoctoproject.org/show_bug.cgi?id=14141). The main
> goal of this bug is to correctly support git submodules with devtool.
>
> I currently have an almost ready branch here:
> https://git.yoctoproject.org/poky-contrib/log/?h=jstephan/devtool-submodule-fix
>
> I asked Jon Mason (reporter of the bug) to test the branch, he
> confirmed that its working for git submodules (i.e recipes using gitsm
> only) such as vulkan-samples or hafnium (meta-arm), but he also
> pointed out a new issue highlighted by the recipe edk2-firmware: this
> recipe is using gitsm for the primary source then extract another git
> repository inside S.
>
> This issue is not related only to gitsm + git recipes, I reproduced
> this kind of error with   cross-localedef-native recipe, using git +
> git or https + git.  But I think the issue is even more global: as of
> today devtool doesn't properly handle recipes that unpack secondary
> sources inside S. Let suppose we have:
>
> SRC_URI = " \
>   http://.tar.gz \
>   http://.tar.gz;subdir=mysubdir \
> "
> If I need to patch something inside mysubdir I would expect to have
> something like:
> SRC_URI = " \
>   http://.tar.gz \
>   http://.tar.gz;subdir=mysubdir \
>   file://mypatch.patch;patchdir=mysubdir \
> "
> Of course this is working, but if I run devtool modify, create my
> patch and do a devtool finish I would have something like
> SRC_URI = " \
>   http://.tar.gz \
>   http://.tar.gz;subdir=mysubdir \
>   file://mypatch.patch \
> "
> where mypatch.patch will patch files inside mysubdir as if they were
> originally part of the primary source.
> That might be acceptable (but I personally would prefer to have a
> patchir parameter matching the subdir parameter).
> Besides that, there is actually a bug here: trying to modify inside
> devtool a file that was added using file:// will add a new patch AND
> modify the original patch... (Tested on master branch with bzip2 with
> the following: devtool modify bzip2, modify Makefile.am, commit the
> modification, devtool finish bzip2 will create a new patch file AND
> also update the originale Makefile.am inside the recipe space)
>
> But things get really bad when using a git source as secondary source:
> SRC_URI = " \
>   http://.tar.gz \
>   git ://;destsuffix=mysubdir \
> "
> mysubdir gets automatically committed inside the primary source
> ("Commiting changes from do patch"). This is an issue because doing
> "git add" on a git directory adds it as a submodule (in a wrong way,
> the correct way of adding it would be "git submodule add url path").
> Here we end up with a submodule which is not populated into
> .gitmodules then "git submodule foreach" commands just fail.
>
> My hack is to detect that git directories were added after unpack and
> properly add them as submodules (" wip: support git tree extracted
> inside S" in my branch) but I am not 100% satisfied with this because
> it implies that devtool is managing secondary source differently if
> they are git directories or not..
>
> So the long story made short:
> * current implementation of devtool is buggy (at least with the
> scenario described above with bzip2), I may try to work on this latter
> * is the current behaviour of devtool acceptable ? (i.e not adding
> patchir parameter on patches)
> * is my "hack" acceptable to handle git secondary sources as a real
> git submodule?
>
> This is giving me headaches and I would really appreciate the feedback
> of the community on this.
>
> Cheers
> Julien
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61678): https://lists.yoctoproject.org/g/yocto/message/61678
Mute This Topic: https://lists.yoctoproject.org/mt/102509834/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Bitbake error for node js #linux #poky #toolchain #ubuntu #yocto

2023-11-14 Thread Martin Jansa 
You need more ram or at least swap to build nodejs, or restrict
PARALLEL_MAKE for nodejs not to trigger OOMK.

On Tue, Nov 14, 2023 at 11:20 AM  wrote:

> Hi iam trying to build pionix ti AM62x https://github.com/PionixPublic
> EVSE SDK
> Bitbake builds till 99 percent and last module nodejs runs for 2 hours and
> gets error and system experience freeze iam using Linux host machine of
> latest 22.04 version with 500gb of storage and Ram of 16gb
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61677): https://lists.yoctoproject.org/g/yocto/message/61677
Mute This Topic: https://lists.yoctoproject.org/mt/102580846/21656
Mute #poky:https://lists.yoctoproject.org/g/yocto/mutehashtag/poky
Mute #toolchain:https://lists.yoctoproject.org/g/yocto/mutehashtag/toolchain
Mute #ubuntu:https://lists.yoctoproject.org/g/yocto/mutehashtag/ubuntu
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #linux:https://lists.yoctoproject.org/g/yocto/mutehashtag/linux
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Bitbake error for node js #linux #poky #toolchain #ubuntu #yocto

2023-11-14 Thread sairajlp99 
Hi iam trying to build pionix ti AM62x https://github.com/PionixPublic EVSE SDK
Bitbake builds till 99 percent and last module nodejs runs for 2 hours and gets 
error and system experience freeze iam using Linux host machine of latest 22.04 
version with 500gb of storage and Ram of 16gb

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61676): https://lists.yoctoproject.org/g/yocto/message/61676
Mute This Topic: https://lists.yoctoproject.org/mt/102580846/21656
Mute #poky:https://lists.yoctoproject.org/g/yocto/mutehashtag/poky
Mute #toolchain:https://lists.yoctoproject.org/g/yocto/mutehashtag/toolchain
Mute #ubuntu:https://lists.yoctoproject.org/g/yocto/mutehashtag/ubuntu
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #linux:https://lists.yoctoproject.org/g/yocto/mutehashtag/linux
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [yocto-autobuilder-helper] Add toaster test builder

2023-11-14 Thread Richard Purdie 
On Mon, 2023-11-13 at 22:30 +, Richard Purdie via
lists.yoctoproject.org wrote:
> On Mon, 2023-11-13 at 13:21 -0500,
> alexander.lussier-cul...@savoirfairelinux.com wrote:
> > From: Alexander Lussier-Cullen 
> > 
> > 
> > Add a toaster test builder that runs the tox test suite using a new
> > run-toaster-tests script.
> > 
> > Signed-off-by: Alexander Lussier-Cullen 
> > 
> > CC: richard.pur...@linuxfoundation.org
> > ---
> >  config.json   |  3 +++
> >  scripts/run-toaster-tests | 22 ++
> >  2 files changed, 25 insertions(+)
> >  create mode 100644 scripts/run-toaster-tests
> > 
> > diff --git a/config.json b/config.json
> > index d10a3a8..0c581d1 100644
> > --- a/config.json
> > +++ b/config.json
> > @@ -1675,6 +1675,9 @@
> >  "step1" : {
> >  "BBTARGETS" : "core-image-patchtest"
> >  }
> > +},
> > +"toaster" : {
> > +"EXTRACMDS" : ["${SCRIPTSDIR}/run-toaster-tests 
> > ${HELPERBUILDDIR} ${HELPERBUILDDIR}/.."]
> >  }
> >  },
> >  "repo-defaults" : {
> > diff --git a/scripts/run-toaster-tests b/scripts/run-toaster-tests
> > new file mode 100644
> > index 000..a785c36
> > --- /dev/null
> > +++ b/scripts/run-toaster-tests
> > @@ -0,0 +1,22 @@
> > +#!/bin/bash
> > +#
> > +# SPDX-License-Identifier: GPL-2.0-only
> > +#
> > +# Called with $1 as the build directory
> > +# $2 as the path to poky
> > +
> > +set -e
> > +set -u
> > +set -o pipefail
> > +set -x
> > +
> > +builddir=$(realpath "$1")
> > +pokydir=$(realpath "$2")
> > +
> > +cd $builddir
> > +mkdir -p toaster_logs
> > +python3 -m venv venv --without-pip --system-site-packages
> > +source venv/bin/activate
> > +python3 -m pip install tox
> > +
> > +tox -c $pokydir/bitbake/lib/toaster/tox.ini
> 
> Thanks! I tested this and the first issue was:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/161/builds/1
> 
> so I added a chmod a+x onto the commit which is on master-next of
> yocto-autobuilder-helper.
> 
> This lead to:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/161/builds/2
> and
> https://autobuilder.yoctoproject.org/typhoon/#/builders/161/builds/3
> 
> which were because a worker with python 3.8/3.9/3.10 wasn't available
> at the time of testing and I'm not restricting the worker set the
> target is using.
> 
> I put a commit onto bitbake/poky master-next to add 3.11 and 3.12 to
> tox.ini which leads to:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/161/builds/4
> 
> which does appear to be running some testing with some errors.
> 
> So we're making progress :)

https://autobuilder.yoctoproject.org/typhoon/#/builders/161/builds/4

(on ubuntu 23.04 with python3.11) ran to completion in 45 minutes,
failures=2, errors=18. 

It'd note that it didn't use SSTATE_DIR or DL_DIR from the parent
environment which is partly why it was so slow, we need to fix that.

I tried adding some of the pending toaster patches to master-next and
rebuilding. There were more workers available so it tried some
different combinations which failed:

https://autobuilder.yoctoproject.org/typhoon/#/builders/161/builds/5

opensuse 15.4 python 3.11

  File "/home/pokybuild/yocto-
worker/toaster/build/build/.tox/py311/lib/python3.11/site-
packages/django/utils/timezone.py", line 12, in 
from backports import zoneinfo
ModuleNotFoundError: No module named 'backports'

https://autobuilder.yoctoproject.org/typhoon/#/builders/161/builds/6

ubuntu 20.04 python 3.8

  File "/usr/lib/python3.8/importlib/metadata.py", line 79, in load
return functools.reduce(getattr, attrs, module)
AttributeError: module 
'virtualenv.create.via_global_ref.builtin.cpython.mac_os' has no attribute 
'CPython2macOsFramework'


I've set https://autobuilder.yoctoproject.org/typhoon/#/builders/161/builds/7
on ubuntu 23.04 away so we can see if things improve or not with the patches.

Cheers,

Richard






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61675): https://lists.yoctoproject.org/g/yocto/message/61675
Mute This Topic: https://lists.yoctoproject.org/mt/102567727/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: 
https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-