|
Re: [meta-zephyr][PATCH 0/4] Add script for version upgrades
Jon Mason
On Fri, Sep 16, 2022 at 10:03:14AM +0100, Peter Hoyes wrote:
From: Peter Hoyes <Peter.Hoyes@...>Series passes CI (on top of the v2.7.3 patch). See https://gitlab.com/jonmason00/meta-zephyr/-/pipelines/645914527 Tested-by: Jon Mason <jon.mason@...>
|
||||
|
|
||||
|
Re: Help and ideas wanted - error during do_package
Richard Purdie
On Tue, 2022-09-20 at 23:05 +0200, Peter Bergin wrote:
Hi,Have you tried putting a: chown root.root ${D}<files> into do_install and checking if you force the ownership, whether that helps? Cheers, Richard |
||||
|
|
||||
|
Help and ideas wanted - error during do_package
Peter Bergin
Hi,
I'm working on a recipe for libtraceevent (https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git) that is needed for newer trace-cmd. I'm confused about an error I get during do_package that I want some help with. File: '<snip>/sources/poky/meta/lib/oe/sstatesig.py', lineno: 587, function: process 0583: else: 0584: add_perm(stat.S_IXOTH, 'x') 0585: 0586: try: *** 0587: update_hash(" %10s" % pwd.getpwuid(s.st_uid).pw_name) 0588: update_hash(" %10s" % grp.getgrgid(s.st_gid).gr_name) 0589: except KeyError as e: 0590: bb.warn("KeyError in %s" % path) 0591: msg = ("KeyError: %s\nPath %s is owned by uid %d, gid %d, which doesn't match " Exception: Exception: KeyError: 'getpwuid(): uid not found: 1000' Path ./package/usr/lib/libtraceevent.a is owned by uid 1000, gid 1004, which doesn't match any user/group on target. This may be due to host contamination. ERROR: Logfile of failure stored in: <snip>/build/<machine>/tmp/work/cortexa53-crypto-poky-linux/libtraceevent/1.6.2-r0/temp/log.do_package.3574262 ERROR: Task (<snip>/sources/meta-openembedded/meta-oe/recipes-kernel/trace-cmd/libtraceevent_1.6.2.bb:do_package) failed with exit code '1' What happens is that during do_package the directory ${WORKDIR}/package is moved to ${WORKDIR}/sstate-build-package and the sstate is calculated. In that sequence in sstatesig.py the owner of the files are checked and used in the hash calculations. By adding debug prints I have seen that in normal case the s.st_uid in the code above evaluates to 0 for the files and directories. When looking in the file system my user (1000/1004) owns them but I guess PSEUDO is involved here to fake root? For some reason when checking the libraries build by libtraceevent in ./usr/lib/ the files reports to be owned by uid 1000 and the exection above is raised. It is valid for ./usr/lib/libtraceevent.a and also other files in the ./usr/lib directory. Before the files in ./usr/lib is checked files from /usr/include has been checked for libtraceevent and they have s.st_uid=0. I've spent some time trying to understand this. Give up now and try this forum if I can get some ideas. I share the recipe below. Thanks /Peter $ cat ../../sources/meta-openembedded/meta-oe/recipes-kernel/trace-cmd/libtraceevent_1.6.2.bb SUMMARY = "Library that provides APIs to access kernel tracepoint events" LICENSE = "GPL-2.0-only & LGPL-2.1-only" LIC_FILES_CHKSUM = " \ file://LICENSES/GPL-2.0;md5=e6a75371ba4d16749254a51215d13f97 \ file://LICENSES/LGPL-2.1;md5=b370887980db5dd40659b50909238dbd \ " SRC_URI = " \ git://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git;branch=libtraceevent;protocol=https \ file://0001-libtraceevent-make-it-possible-to-set-libdir-and-man.patch \ " SRCREV = "424b11f6c3ab2e3bb199180e142fbcf9eebf2ac3" S = "${WORKDIR}/git" do_install () { oe_runmake 'DESTDIR=${D}' install } FILES:${PN} += "${libdir}/traceevent/plugins" $ cat ../../sources/meta-openembedded/meta-oe/recipes-kernel/trace-cmd/files/0001-libtraceevent-make-it-possible-to-set-libdir-and-man.patch From 2014d037d3488f1a53e1c0c83263e77322ac14ef Mon Sep 17 00:00:00 2001 From: Peter Bergin <peter@...> Date: Mon, 19 Sep 2022 17:21:28 +0200 Subject: [PATCH] libtraceevent: make it possible to set libdir and mandir from outside When building in build frameworks such as openembedded it is desired to use the defintion of libdir and mandir from the build framework. Signed-off-by: Peter Bergin <peter@...> --- Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index 194bbdd..aa1984d 100644 --- a/Makefile +++ b/Makefile @@ -45,8 +45,8 @@ endif libdir_relative ?= $(libdir_relative_temp) prefix ?= /usr/local -libdir = $(prefix)/$(libdir_relative) -man_dir = $(prefix)/share/man +libdir ?= $(prefix)/$(libdir_relative) +man_dir ?= $(prefix)/share/man man_dir_SQ = '$(subst ','\'',$(man_dir))' pkgconfig_dir ?= $(word 1,$(shell $(PKG_CONFIG) \ --variable pc_path pkg-config | tr ":" " ")) -- 2.34.1 |
||||
|
|
||||
|
Re: [meta-zephyr][PATCH] zephyr-kernel/2.7: update to zephyr v2.7.3
Jon Mason
On Thu, Sep 15, 2022 at 03:20:42PM +0800, Naveen Saini wrote:
003de78ce0 release: Zephyr 2.7.3Passes CI https://gitlab.com/jonmason00/meta-zephyr/-/pipelines/645876493 Tested-by: Jon Mason <jon.mason@...> --- |
||||
|
|
||||
|
[meta-zephyr][PATCH 2/3] zephyr-bsp/qemu-cortex-m3: update to use new path
Jon Mason
Update the qemu-cortex-m3 machine to use the OE tune file, and remove
the duplicate one locally. Signed-off-by: Jon Mason <jon.mason@...> --- .../conf/machine/include/tune-cortexm3.inc | 21 ------------------- .../conf/machine/qemu-cortex-m3.conf | 2 +- 2 files changed, 1 insertion(+), 22 deletions(-) delete mode 100644 meta-zephyr-bsp/conf/machine/include/tune-cortexm3.inc diff --git a/meta-zephyr-bsp/conf/machine/include/tune-cortexm3.inc b/meta-zephyr-bsp/conf/machine/include/tune-cortexm3.inc deleted file mode 100644 index 404e2b7..0000000 --- a/meta-zephyr-bsp/conf/machine/include/tune-cortexm3.inc +++ /dev/null @@ -1,21 +0,0 @@ -DEFAULTTUNE ?= "cortexm3" - -require conf/machine/include/arm/arch-armv7a.inc - -TUNEVALID[cortexm3] = "Enable Cortex-M3 specific processor optimizations" -TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexm3', ' -mcpu=cortex-m3', '', d)}" -AVAILTUNES += "cortexm3" - -TUNEVALID[armv7m] = "Enable Cortex-M3 specific processor optimizations" -TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'armv7m', ' -march=armv7-m', '', d)}" -MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'armv7m', 'armv7m:', '' ,d)}" - -TUNE_PKGARCH:tune-cortexm3 = "cortexm3" - -ARMPKGARCH:tune-cortexm3 = "armv7m" -PACKAGE_EXTRA_ARCHS:tune-cortexm3 ="cortexm3" - -TUNE_FEATURES:tune-cortexm3 = "armv7m vfp cortexm3" -PACKAGE_EXTRA_ARCHS:tune-cortexm3 = "${PACKAGE_EXTRA_ARCHS:tune-armv7at} armv7m-vfp" - -TUNE_CCARGS_MFLOAT = "soft" diff --git a/meta-zephyr-bsp/conf/machine/qemu-cortex-m3.conf b/meta-zephyr-bsp/conf/machine/qemu-cortex-m3.conf index 835a775..989f2ca 100644 --- a/meta-zephyr-bsp/conf/machine/qemu-cortex-m3.conf +++ b/meta-zephyr-bsp/conf/machine/qemu-cortex-m3.conf @@ -3,7 +3,7 @@ #@DESCRIPTION: Machine for Zephyr BOARD qemu_cortex_m3 require conf/machine/include/qemu.inc -require conf/machine/include/tune-cortexm3.inc +require conf/machine/include/arm/armv7m/tune-cortexm3.inc ZEPHYR_INHERIT_CLASSES += "zephyr-qemuboot" -- 2.17.1 |
||||
|
|
||||
|
[meta-zephyr][PATCH 1/3] zephyr-bsp: remove unused tune file
Jon Mason
Signed-off-by: Jon Mason <jon.mason@...>
--- .../conf/machine/include/tune-cortexm0.inc | 31 ------------------- 1 file changed, 31 deletions(-) delete mode 100644 meta-zephyr-bsp/conf/machine/include/tune-cortexm0.inc diff --git a/meta-zephyr-bsp/conf/machine/include/tune-cortexm0.inc b/meta-zephyr-bsp/conf/machine/include/tune-cortexm0.inc deleted file mode 100644 index 5067eb2..0000000 --- a/meta-zephyr-bsp/conf/machine/include/tune-cortexm0.inc +++ /dev/null @@ -1,31 +0,0 @@ -DEFAULTTUNE ?= "cortexm0" - -require conf/machine/include/arm/arch-armv6.inc - -TUNEVALID[cortexm0] = "Enable Cortex-M0 specific processor optimizations" -TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexm0', ' -mcpu=cortex-m0', '', d)}" -AVAILTUNES += "cortexm0" - -TUNEVALID[no-thumb-interwork] = "Enable thumb mode" -TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'no-thumb-interwork', ' -mno-thumb-interwork', '', d)}" -AVAILTUNES += "no-thumb-interwork" - -TUNEVALID[no-ffast-math] = "Enable thumb mode" -TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'no-ffast-math', ' -fno-fast-math', '', d)}" -AVAILTUNES += "no-ffast-math" - -TUNEVALID[soft] = "Enable thumb mode" -TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'soft', ' -mfloat-abi=soft', '', d)}" -AVAILTUNES += "soft" - -TUNEVALID[armv6m] = "Enable Cortex-M0 specific processor optimizations" -TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'armv6m', ' -march=armv6-m', '', d)}" -MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'armv6m', 'armv6m:', '' ,d)}" - -ARMPKGARCH:tune-cortexm0 = "cortexm0" -TUNE_FEATURES:tune-cortexm0 = "${TUNE_FEATURES:tune-armv6} cortexm0" - -PACKAGE_EXTRA_ARCHS:tune-cortexm0 = "${PACKAGE_EXTRA_ARCHS:tune-armv6m} cortexm0-vfp" - -TUNE_FEATURES:tune-cortexm0 = "armv6m vfp cortexm0 thumb no-thumb-interwork soft" - -- 2.17.1 |
||||
|
|
||||
|
[meta-zephyr][PATCH 3/3] zephyr-bsp: update cortex-m4's to use new path
Jon Mason
Update the machines using cortex m4s to use the OE tune file, and remove
the duplicate one locally. Signed-off-by: Jon Mason <jon.mason@...> --- .../conf/machine/include/nrf52.inc | 4 ++-- .../machine/include/stm32mp1-cortex-m4.inc | 4 ++-- .../conf/machine/include/tune-cortexm4.inc | 19 ------------------- 3 files changed, 4 insertions(+), 23 deletions(-) delete mode 100644 meta-zephyr-bsp/conf/machine/include/tune-cortexm4.inc diff --git a/meta-zephyr-bsp/conf/machine/include/nrf52.inc b/meta-zephyr-bsp/conf/machine/include/nrf52.inc index 4162d3e..bd72195 100644 --- a/meta-zephyr-bsp/conf/machine/include/nrf52.inc +++ b/meta-zephyr-bsp/conf/machine/include/nrf52.inc @@ -3,9 +3,9 @@ #@DESCRIPTION: Machine configuration for Nordic Semiconductor nRF52xxx (Cortex-M4) SoC. -require conf/machine/include/tune-cortexm4.inc +require conf/machine/include/arm/armv7m/tune-cortexm4.inc -TUNE_FEATURES = "armv7m cortexm4" +TUNE_FEATURES = "armv7em cortexm4" # Target type for this machine used by Pyocd PYOCD_TARGET = "nrf52" diff --git a/meta-zephyr-bsp/conf/machine/include/stm32mp1-cortex-m4.inc b/meta-zephyr-bsp/conf/machine/include/stm32mp1-cortex-m4.inc index 0d46620..94b2e05 100644 --- a/meta-zephyr-bsp/conf/machine/include/stm32mp1-cortex-m4.inc +++ b/meta-zephyr-bsp/conf/machine/include/stm32mp1-cortex-m4.inc @@ -3,6 +3,6 @@ #@DESCRIPTION: Machine configuration for Cortex-M4 core of STMicroelectronics STM32MP1 SoC. -require conf/machine/include/tune-cortexm4.inc +require conf/machine/include/arm/armv7m/tune-cortexm4.inc -TUNE_FEATURES = "armv7m cortexm4" +TUNE_FEATURES = "armv7em cortexm4" diff --git a/meta-zephyr-bsp/conf/machine/include/tune-cortexm4.inc b/meta-zephyr-bsp/conf/machine/include/tune-cortexm4.inc deleted file mode 100644 index b3092d8..0000000 --- a/meta-zephyr-bsp/conf/machine/include/tune-cortexm4.inc +++ /dev/null @@ -1,19 +0,0 @@ -DEFAULTTUNE ?= "cortexm4" - -require conf/machine/include/arm/arch-armv7a.inc - -TUNEVALID[cortexm4] = "Enable Cortex-M4 specific processor optimizations" -TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexm4', ' -mcpu=cortex-m4', '', d)}" -AVAILTUNES += "cortexm4" - -TUNEVALID[armv7m] = "Enable Cortex-M4 specific processor optimizations" -TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'armv7m', ' -march=armv7e-m', '', d)}" -MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'armv7m', 'armv7m:', '' ,d)}" - -TUNE_PKGARCH:tune-cortexm4 = "cortexm4" - -ARMPKGARCH:tune-cortexm4 = "armv7m" -PACKAGE_EXTRA_ARCHS:tune-cortexm4 ="cortexm4" - -TUNE_FEATURES:tune-cortexm4 = "armv7m vfp cortexm4" -PACKAGE_EXTRA_ARCHS:tune-cortexm4 = "${PACKAGE_EXTRA_ARCHS:tune-armv7at} armv7m-vfp armv7m" -- 2.17.1 |
||||
|
|
||||
|
[meta-zephyr][PATCH 2/2] zephyr-bsp: zephyr parameters update
Jon Mason
Update the parameters being run in qemu to get more stable results.
Values taken from zephyr qemu. Also, use QB_GRAPHICS instead of QB_OPT_APPEND for the relevant places. Signed-off-by: Jon Mason <jon.mason@...> --- .gitlab-ci.yml | 3 ++- ci/qemu-cortex-m3.yml | 6 ------ meta-zephyr-bsp/conf/machine/qemu-cortex-a53.conf | 2 +- meta-zephyr-bsp/conf/machine/qemu-cortex-m0.conf | 4 ++-- meta-zephyr-bsp/conf/machine/qemu-cortex-m3.conf | 3 ++- meta-zephyr-bsp/conf/machine/qemu-cortex-r5.conf | 2 +- meta-zephyr-bsp/conf/machine/qemu-x86.conf | 2 +- 7 files changed, 9 insertions(+), 13 deletions(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index e0bf84e..082cd44 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -88,7 +88,8 @@ qemu-cortex-m0: extends: .build parallel: matrix: - - TESTING: testimage + - TOOLCHAIN: [default, zephyr-toolchain] + TESTING: testimage qemu-cortex-m3: extends: .build diff --git a/ci/qemu-cortex-m3.yml b/ci/qemu-cortex-m3.yml index b01480c..46fd551 100644 --- a/ci/qemu-cortex-m3.yml +++ b/ci/qemu-cortex-m3.yml @@ -3,10 +3,4 @@ header: includes: - ci/base.yml -local_conf_header: - nonbuilding_tests: | - ZEPHYRTESTS:remove = "common context pending poll sleep" - qemu_opts: | - QB_OPT_APPEND = "-icount shift=3,align=off,sleep=on -rtc clock=vm" - machine: qemu-cortex-m3 diff --git a/meta-zephyr-bsp/conf/machine/qemu-cortex-a53.conf b/meta-zephyr-bsp/conf/machine/qemu-cortex-a53.conf index 97e536e..e21f3da 100644 --- a/meta-zephyr-bsp/conf/machine/qemu-cortex-a53.conf +++ b/meta-zephyr-bsp/conf/machine/qemu-cortex-a53.conf @@ -11,7 +11,7 @@ TCLIBC = "newlib" QB_SYSTEM_NAME = "qemu-system-aarch64" QB_MACHINE = "-machine virt,secure=on,gic-version=3" QB_CPU = "-cpu cortex-a53" -QB_OPT_APPEND = "-nographic -vga none" +QB_GRAPHICS = "-nographic -vga none" QB_OPT_APPEND = "-icount shift=4,align=off,sleep=on -rtc clock=vm" # Zephyr RTOS settings diff --git a/meta-zephyr-bsp/conf/machine/qemu-cortex-m0.conf b/meta-zephyr-bsp/conf/machine/qemu-cortex-m0.conf index 1cf2bb0..736579e 100644 --- a/meta-zephyr-bsp/conf/machine/qemu-cortex-m0.conf +++ b/meta-zephyr-bsp/conf/machine/qemu-cortex-m0.conf @@ -14,9 +14,9 @@ TCLIBC = "newlib" QB_SYSTEM_NAME = "qemu-system-arm" QB_MACHINE = "-machine microbit" QB_CPU = "-cpu cortex-m0" -QB_OPT_APPEND = "-nographic -vga none" +QB_GRAPHICS = "-nographic -vga none" QB_RNG = "" -QB_OPT_APPEND = "-icount shift=6,align=off,sleep=on -rtc clock=vm" +QB_OPT_APPEND = "-icount shift=6,align=off,sleep=off -rtc clock=vm" # Zephyr RTOS settings ZEPHYR_BOARD = "qemu_cortex_m0" diff --git a/meta-zephyr-bsp/conf/machine/qemu-cortex-m3.conf b/meta-zephyr-bsp/conf/machine/qemu-cortex-m3.conf index 835a775..e6edefb 100644 --- a/meta-zephyr-bsp/conf/machine/qemu-cortex-m3.conf +++ b/meta-zephyr-bsp/conf/machine/qemu-cortex-m3.conf @@ -10,8 +10,9 @@ ZEPHYR_INHERIT_CLASSES += "zephyr-qemuboot" # For runqemu QB_SYSTEM_NAME = "qemu-system-arm" QB_MACHINE = "-machine lm3s6965evb" -QB_OPT_APPEND = "-nographic -vga none" +QB_GRAPHICS = "-nographic -vga none" QB_CPU = "-cpu cortex-m3" QB_RNG = "" +QB_OPT_APPEND = "-icount shift=6,align=off,sleep=off -rtc clock=vm" ARCH:qemu-cortex-m3 = "arm" diff --git a/meta-zephyr-bsp/conf/machine/qemu-cortex-r5.conf b/meta-zephyr-bsp/conf/machine/qemu-cortex-r5.conf index 29b37d7..5a0ea69 100644 --- a/meta-zephyr-bsp/conf/machine/qemu-cortex-r5.conf +++ b/meta-zephyr-bsp/conf/machine/qemu-cortex-r5.conf @@ -13,7 +13,7 @@ QB_SYSTEM_NAME = "qemu-system-aarch64" QB_MACHINE = "-machine xlnx-zcu102" QB_CPU = "-cpu cortex-r5" QB_MEM = "-m 64k" -QB_OPT_APPEND = "-nographic -vga none" +QB_GRAPHICS = "-nographic -vga none" QB_RNG = "" # Zephyr RTOS settings diff --git a/meta-zephyr-bsp/conf/machine/qemu-x86.conf b/meta-zephyr-bsp/conf/machine/qemu-x86.conf index ae7716c..0333d7c 100644 --- a/meta-zephyr-bsp/conf/machine/qemu-x86.conf +++ b/meta-zephyr-bsp/conf/machine/qemu-x86.conf @@ -10,7 +10,7 @@ ZEPHYR_INHERIT_CLASSES += "zephyr-qemuboot" # For runqemu QB_SYSTEM_NAME = "qemu-system-i386" QB_MACHINE = "-machine type=pc-q35-2.10" -QB_OPT_APPEND = "-nographic -no-acpi" +QB_GRAPHICS = "-nographic -no-acpi" QB_CPU:x86 = "-cpu qemu32,+nx,+pae" QB_CPU_KVM:x86 = "-cpu kvm32" -- 2.17.1 |
||||
|
|
||||
|
[meta-zephyr][PATCH 1/2] zephyr-bsp/qemu-cortex-a53: run testimage
Jon Mason
Make the changes necessary to get testimage working and run it as part
of CI Signed-off-by: Jon Mason <jon.mason@...> --- .gitlab-ci.yml | 1 + ci/qemu-cortex-a53.yml | 4 ++++ meta-zephyr-bsp/conf/machine/qemu-cortex-a53.conf | 3 ++- 3 files changed, 7 insertions(+), 1 deletion(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 145aefd..e0bf84e 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -82,6 +82,7 @@ qemu-cortex-a53: parallel: matrix: - TOOLCHAIN: [default, zephyr-toolchain] + TESTING: testimage qemu-cortex-m0: extends: .build diff --git a/ci/qemu-cortex-a53.yml b/ci/qemu-cortex-a53.yml index e77da8b..ca8b649 100644 --- a/ci/qemu-cortex-a53.yml +++ b/ci/qemu-cortex-a53.yml @@ -3,4 +3,8 @@ header: includes: - ci/base.yml +local_conf_header: + failing_tests: | + ZEPHYRTESTS:remove = "interrupt" + machine: qemu-cortex-a53 diff --git a/meta-zephyr-bsp/conf/machine/qemu-cortex-a53.conf b/meta-zephyr-bsp/conf/machine/qemu-cortex-a53.conf index b97cde7..97e536e 100644 --- a/meta-zephyr-bsp/conf/machine/qemu-cortex-a53.conf +++ b/meta-zephyr-bsp/conf/machine/qemu-cortex-a53.conf @@ -9,9 +9,10 @@ TCLIBC = "newlib" # For runqemu QB_SYSTEM_NAME = "qemu-system-aarch64" -QB_MACHINE = "-machine virt" +QB_MACHINE = "-machine virt,secure=on,gic-version=3" QB_CPU = "-cpu cortex-a53" QB_OPT_APPEND = "-nographic -vga none" +QB_OPT_APPEND = "-icount shift=4,align=off,sleep=on -rtc clock=vm" # Zephyr RTOS settings ZEPHYR_BOARD = "qemu_cortex_a53" -- 2.17.1 |
||||
|
|
||||
|
Is there a way to prevent bitbake from trying to demand dependencies it comes up with based on installed files?
Kuba Sanak
Hi all, First time posting to this mailing list, hope this email kind of email is what it’s for! Background / what I'm doing: I'm creating an image which uses a docker to do stuff. Loading new docker images takes a long time on my target so I have created a recipe which essentially pre-loads docker store with the said docker image at build time and installs it on the target filesystem, so that it can just spin the container up from it after being flashed. Yocto version Hardknott is being used. The problem: the resulting docker store I'm installing on the target (at `/var/lib/docker`) contains the filesystem of the container. Some files in that filesystem have dependencies which are satisfied internally when that filesystem exists as a docker container. However, bitbake is trying to be clever and shouts at me for those dependencies not being satisfied overall. Building the docker-image recipe by itself works fine, but when I include it in the whole image for my target I get errors which essentially amount to Error: Problem: conflicting requests - nothing provides /usr/bin/python2.6 needed by my-docker-image-baked-in-1.0+git0+14055cb562-r0.cortexa53_crypto - nothing provides libEGL.so needed by my-docker-image-baked-in-1.0+git0+14055cb562-r0.cortexa53_crypto etc... Which are false alarms as those files are indeed extant at my in my docker store and in the docker container being spun up. I've spent so much time now trying to find out how to prevent bitbake from trying to save me from myself, but simply found no way to coax it into believing me that I really don't need those dependencies. Is there any way to actually convince it those are not needed? Or to prevent package created by my docker-store-constructing recipe from picking up those fake dependancies? Best, Kuba |
||||
|
|
||||
|
Monsees, Steven C (US)
Thanks… will give it a try.
From: Ross Burton <Ross.Burton@...>
Sent: Tuesday, September 20, 2022 11:38 AM To: Monsees, Steven C (US) <steven.monsees@...>; yocto@... Subject: Re: [yocto] #yocto #dunfell
Hi,
SBSA is EDK2 based, which is basically incredibly painful to patch. The source files are windows-style CR/LF so your patch needs to have CR/LF, but if the whole patch has CR/LF then git “helpfully” transforms the patch to just unix-style LF, which doesn’t apply.
The “solution” (workaround) is to convert the patch to LF encoding, and manually add the CR characters to the end of each line in the patch body.
The good news is that EDK2 is moving to LF encoding, so this will be solved at some point.
Ross
From:
yocto@... <yocto@...> on behalf of Monsees, Steven C (US) via lists.yoctoproject.org
<steven.monsees=baesystems.com@...>
Any hints or ideas on what I might be doing wrong would be appreciated…
I am seeing an error when I attempt to apply a patch, and could use some clarification or way to resolve…
Am doing something wrong in patch creation ? What is meant by : ”Patch console.patch does not apply (enforce with -f)” ? How can I best resolve this issue ?
I edited a file in the recipe’s git repo in order to create the patch for the change:
git diff -u console.c
which I used as my patch:
diff --git a/lib/console.c b/lib/console.c index 9c10560..b932a44 100644 --- a/lib/console.c +++ b/lib/console.c @@ -357,7 +357,7 @@ static struct { { EFI_SECURITY_VIOLATION, L"Security Violation"},
// warnings - { EFI_WARN_UNKOWN_GLYPH, L"Warning Unknown Glyph"}, + { EFI_WARN_UNKNOWN_GLYPH, L"Warning Unknown Glyph"}, { EFI_WARN_DELETE_FAILURE, L"Warning Delete Failure"}, { EFI_WARN_WRITE_FAILURE, L"Warning Write Failure"}, { EFI_WARN_BUFFER_TOO_SMALL, L"Warning Buffer Too Small"},
I am getting the following error when the patch is applied:
ERROR: efitools-native-1.7.0+gitAUTOINC+0649468475-r0 do_patch: Applying patch 'console.patch' on target directory '/disk0/scratch/yocto/workspace/poky-dunfell-23.0.19/builds/sbca-default/tmp/work/x86_64-linux/efitools-native/1.7.0+gitAUTOINC+0649468475-r0/git' Command Error: 'quilt --quiltrc /disk0/scratch/yocto/workspace/poky-dunfell-23.0.19/builds/sbca-default/tmp/work/x86_64-linux/efitools-native/1.7.0+gitAUTOINC+0649468475-r0/recipe-sysroot-native/etc/quiltrc push' exited with 0 Output: Applying patch console.patch patching file lib/console.c Hunk #1 FAILED at 357. 1 out of 1 hunk FAILED -- rejects in file lib/console.c Patch console.patch does not apply (enforce with -f) ERROR: Logfile of failure stored in: /disk0/scratch/yocto/workspace/poky-dunfell-23.0.19/builds/sbca-default/tmp/work/x86_64-linux/efitools-native/1.7.0+gitAUTOINC+0649468475-r0/temp/log.do_patch.7615 ERROR: Task (/disk0/scratch/yocto/workspace/poky-dunfell-23.0.19/meta-bae/meta-limws/meta-intel/meta-sbca/recipes-bsp/efitools/efitools-native_git.bb:do_patch) failed with exit code '1'
Thanks, Steve |
||||
|
|
||||
|
Hi,
SBSA is EDK2 based, which is basically incredibly painful to patch. The source files are windows-style CR/LF so your patch needs to have CR/LF, but if the whole patch has CR/LF then git “helpfully” transforms the patch to just unix-style LF, which doesn’t apply.
The “solution” (workaround) is to convert the patch to LF encoding, and manually add the CR characters to the end of each line in the patch body.
The good news is that EDK2 is moving to LF encoding, so this will be solved at some point.
Ross
From:
yocto@... <yocto@...> on behalf of Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@...>
Any hints or ideas on what I might be doing wrong would be appreciated…
From: yocto@... <yocto@...>
On Behalf Of Monsees, Steven C (US) via lists.yoctoproject.org
Sent: Monday, September 19, 2022 2:22 PM To: yocto@... Subject: [yocto] #yocto #dunfell
I am seeing an error when I attempt to apply a patch, and could use some clarification or way to resolve…
Am doing something wrong in patch creation ? What is meant by : ”Patch console.patch does not apply (enforce with -f)” ? How can I best resolve this issue ?
I edited a file in the recipe’s git repo in order to create the patch for the change:
git diff -u console.c
which I used as my patch:
diff --git a/lib/console.c b/lib/console.c index 9c10560..b932a44 100644 --- a/lib/console.c +++ b/lib/console.c @@ -357,7 +357,7 @@ static struct { { EFI_SECURITY_VIOLATION, L"Security Violation"},
// warnings - { EFI_WARN_UNKOWN_GLYPH, L"Warning Unknown Glyph"}, + { EFI_WARN_UNKNOWN_GLYPH, L"Warning Unknown Glyph"}, { EFI_WARN_DELETE_FAILURE, L"Warning Delete Failure"}, { EFI_WARN_WRITE_FAILURE, L"Warning Write Failure"}, { EFI_WARN_BUFFER_TOO_SMALL, L"Warning Buffer Too Small"},
I am getting the following error when the patch is applied:
ERROR: efitools-native-1.7.0+gitAUTOINC+0649468475-r0 do_patch: Applying patch 'console.patch' on target directory '/disk0/scratch/yocto/workspace/poky-dunfell-23.0.19/builds/sbca-default/tmp/work/x86_64-linux/efitools-native/1.7.0+gitAUTOINC+0649468475-r0/git' Command Error: 'quilt --quiltrc /disk0/scratch/yocto/workspace/poky-dunfell-23.0.19/builds/sbca-default/tmp/work/x86_64-linux/efitools-native/1.7.0+gitAUTOINC+0649468475-r0/recipe-sysroot-native/etc/quiltrc push' exited with 0 Output: Applying patch console.patch patching file lib/console.c Hunk #1 FAILED at 357. 1 out of 1 hunk FAILED -- rejects in file lib/console.c Patch console.patch does not apply (enforce with -f) ERROR: Logfile of failure stored in: /disk0/scratch/yocto/workspace/poky-dunfell-23.0.19/builds/sbca-default/tmp/work/x86_64-linux/efitools-native/1.7.0+gitAUTOINC+0649468475-r0/temp/log.do_patch.7615 ERROR: Task (/disk0/scratch/yocto/workspace/poky-dunfell-23.0.19/meta-bae/meta-limws/meta-intel/meta-sbca/recipes-bsp/efitools/efitools-native_git.bb:do_patch) failed with exit code '1'
Thanks, Steve |
||||
|
|
||||
|
Monsees, Steven C (US)
Any hints or ideas on what I might be doing wrong would be appreciated…
From: yocto@... <yocto@...>
On Behalf Of Monsees, Steven C (US) via lists.yoctoproject.org
Sent: Monday, September 19, 2022 2:22 PM To: yocto@... Subject: [yocto] #yocto #dunfell
I am seeing an error when I attempt to apply a patch, and could use some clarification or way to resolve…
Am doing something wrong in patch creation ? What is meant by : ”Patch console.patch does not apply (enforce with -f)” ? How can I best resolve this issue ?
I edited a file in the recipe’s git repo in order to create the patch for the change:
git diff -u console.c
which I used as my patch:
diff --git a/lib/console.c b/lib/console.c index 9c10560..b932a44 100644 --- a/lib/console.c +++ b/lib/console.c @@ -357,7 +357,7 @@ static struct { { EFI_SECURITY_VIOLATION, L"Security Violation"},
// warnings - { EFI_WARN_UNKOWN_GLYPH, L"Warning Unknown Glyph"}, + { EFI_WARN_UNKNOWN_GLYPH, L"Warning Unknown Glyph"}, { EFI_WARN_DELETE_FAILURE, L"Warning Delete Failure"}, { EFI_WARN_WRITE_FAILURE, L"Warning Write Failure"}, { EFI_WARN_BUFFER_TOO_SMALL, L"Warning Buffer Too Small"},
I am getting the following error when the patch is applied:
ERROR: efitools-native-1.7.0+gitAUTOINC+0649468475-r0 do_patch: Applying patch 'console.patch' on target directory '/disk0/scratch/yocto/workspace/poky-dunfell-23.0.19/builds/sbca-default/tmp/work/x86_64-linux/efitools-native/1.7.0+gitAUTOINC+0649468475-r0/git' Command Error: 'quilt --quiltrc /disk0/scratch/yocto/workspace/poky-dunfell-23.0.19/builds/sbca-default/tmp/work/x86_64-linux/efitools-native/1.7.0+gitAUTOINC+0649468475-r0/recipe-sysroot-native/etc/quiltrc push' exited with 0 Output: Applying patch console.patch patching file lib/console.c Hunk #1 FAILED at 357. 1 out of 1 hunk FAILED -- rejects in file lib/console.c Patch console.patch does not apply (enforce with -f) ERROR: Logfile of failure stored in: /disk0/scratch/yocto/workspace/poky-dunfell-23.0.19/builds/sbca-default/tmp/work/x86_64-linux/efitools-native/1.7.0+gitAUTOINC+0649468475-r0/temp/log.do_patch.7615 ERROR: Task (/disk0/scratch/yocto/workspace/poky-dunfell-23.0.19/meta-bae/meta-limws/meta-intel/meta-sbca/recipes-bsp/efitools/efitools-native_git.bb:do_patch) failed with exit code '1'
Thanks, Steve |
||||
|
|
||||
|
Yocto Project Status 20 September 2022 (WW38)
Stephen Jolley
Current Dev Position: YP 4.1 M4 (Feature Freeze) Next Deadline: 3rd October 2022 YP 4.1 M4 Build
Next Team Meetings:
Key Status/Updates:
Ways to contribute:
YP 4.1 Milestone Dates:
Upcoming dot releases:
Tracking Metrics:
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||
|
|
||||
|
Re: Adding Vulkan to core-image-weston
Alexander Kanavin
What often works is running it under strace - you might be able to see the one key syscall that causes the failure. Otherwise you might have to go through the heavier gdb step through. Alex On Tue 20. Sep 2022 at 10.25, PHIL <heideggm@...> wrote:
|
||||
|
|
||||
|
Re: Adding Vulkan to core-image-weston
Edgar Mobile
Ok it seems to use Software now given how slow weston-simple-egl has become. But vulkaninfo still fails with ERROR_INCOMPATIBLE_DRIVER.
-- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet. |
||||
|
|
||||
|
Re: Adding Vulkan to core-image-weston
Alexander Kanavin
It helps if you say what you did precisely and show the complaint. Alex On Tue 20. Sep 2022 at 9.40, PHIL <heideggm@...> wrote:
|
||||
|
|
||||
|
libsemanage 3.4 issue
Hi,
We are trying to use meta-selinux master branch and I got issue during compilation. nativesdk-libsemanage failed to compile with error: make[1]: Entering directory '<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/git/libsemanage/src' swig -Wall -python -o semanageswig_wrap.c -outdir ./ semanageswig_python.i x86_64-xesdk-linux-gcc --sysroot=<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/recipe-sysroot -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/git/libsemanage=/usr/src/debug/nativesdk-libsemanage/3.4-r0 -fdebug-prefix-map=<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/git/libsemanage=/usr/src/debug/nativesdk-libsemanage/3.4-r0 -fmacro-prefix-map=<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/git/libsemanage=/usr/src/debug/nativesdk-libsemanage/3.4-r0 -fdebug-prefix-map=<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/git/libsemanage=/usr/src/debug/nativesdk-libsemanage/3.4-r0 -fdebug-prefix-map=<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/recipe-sysroot= -fmacro-prefix-map=<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/recipe-sysroot= -fdebug-prefix-map=<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/recipe-sysroot-native= -fmacro-prefix-map=<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/git/libsemanage=/usr/src/debug/nativesdk-libsemanage/3.4-r0 -fdebug-prefix-map=<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/git/libsemanage=/usr/src/debug/nativesdk-libsemanage/3.4-r0 -fmacro-prefix-map=<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/git/libsemanage=/usr/src/debug/nativesdk-libsemanage/3.4-r0 -fdebug-prefix-map=<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/git/libsemanage=/usr/src/debug/nativesdk-libsemanage/3.4-r0 -fdebug-prefix-map=<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/recipe-sysroot= -fmacro-prefix-map=<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/recipe-sysroot= -fdebug-prefix-map=<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/recipe-sysroot-native= -mtune=generic -DDISABLE_AUDIT -I../include -D_GNU_SOURCE -Wno-error -Wno-unused-but-set-variable -Wno-unused-variable -Wno-shadow -Wno-unused-parameter -Wno-missing-prototypes -I<...>/sdk-master-next/build/tmp/work/x86_64-nativesdk-xesdk-linux/nativesdk-libsemanage/3.4-r0/recipe-sysroot/usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-xesdk-linux/usr/include/python3.10 -fPIC -DSHARED -c -o python-3.10semanageswig_wrap.lo semanageswig_wrap.c semanageswig_wrap.c:154:11: fatal error: Python.h: No such file or directory 154 | # include <Python.h> | ^~~~~~~~~~ compilation terminated. It looks like for nativesdk-libsemanage we have implicit dependency on native-python so recipe-sysroot-native populated with python header. But recipe looks for recipe-sysroot for headers. Adding python3 to dependencies fix this issue: -DEPENDS = "libsepol libselinux bison-native swig-native" +DEPENDS = "libsepol libselinux python3 bison-native swig-native" But I'm not sure this is right and probably issue is in global problem of yocto + python cross compilation issues. Regards, Oleksiy |
||||
|
|
||||
|
Re: Adding Vulkan to core-image-weston
Edgar Mobile
What would be the simplest way to achieve that with bitbake? I tried swrast in mesa yesterday but it complained because it wants Gallium.
toggle quoted message
Show quoted text
Am 20. September 2022 10:23:38 MESZ schrieb Alexander Kanavin <alex.kanavin@...>:
-- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet. |
||||
|
|
||||
|
Re: Adding Vulkan to core-image-weston
Alexander Kanavin
Don’t bother with virgl yet. Start with the pure software implementation in Mesa. Alex On Tue 20. Sep 2022 at 8.39, Edgar Mobile <heideggm@...> wrote:
|
||||
|
|