On Mon, 2024-09-02 at 22:31 +0200, Adrian Freihofer via lists.openembedded.org
wrote:
> From: Adrian Freihofer
>
> The kernel-yocto.bbclass defines some tasks tasks and it also adds these
> tasks to the SRCTREECOVEREDTASKS list. There is no need for devtool to
> duplicate this code and override
Hi,
On Mon, Sep 02, 2024 at 06:13:06PM +0200, A. Sverdlin via
lists.openembedded.org wrote:
> From: Alexander Sverdlin
>
> mkimage doesn't fail if it is not able to sign FIT nodes.
> This may lead to unbootable images in secure boot configurations.
> Make signing failures fatal by parsing the m
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/2-2-webkitgtk-Fix-build-issues-with-clang-19.patch
FAIL: test commit message presence: Please include a commit mess
This will fix build with libc++ from llvm 19.x
Signed-off-by: Khem Raj
---
...me-NameString-with-vector-of-uint8_t.patch | 90 +++
...po-in-Name-Name-append-to-ndata_-not.patch | 36
meta/recipes-connectivity/kea/kea_2.6.1.bb| 2 +
3 files changed, 128 insertions(+)
Signed-off-by: Khem Raj
---
...1-Fix-build-issues-with-latest-Clang.patch | 251 ++
meta/recipes-sato/webkit/webkitgtk_2.44.3.bb | 1 +
2 files changed, 252 insertions(+)
create mode 100644
meta/recipes-sato/webkit/webkitgtk/0001-Fix-build-issues-with-latest-Clang.patch
diff
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-5.1_M3.rc1.
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
On 9/2/24 19:04, Robert P. J. Day wrote:
On Mon, 2 Sep 2024, Richard Purdie wrote:
On Mon, 2024-09-02 at 06:39 -0400, Robert P. J. Day via lists.openembedded.org
wrote:
i'm sure i've overlooked something silly, but in building a
qemuarm64 image to demo ptest to some colleagues, poky by def
Improved detection of ioctl API makes it easier to use the right
implementation rather than bunch of ifdef condition checks.
Signed-off-by: Khem Raj
---
...figure-improve-check-for-POSIX-ioctl.patch | 48 +++
.../recipes-multimedia/ffmpeg/ffmpeg_7.0.2.bb | 1 +
2 files changed,
From: Adrian Freihofer
The kernel-yocto.bbclass defines some tasks tasks and it also adds these
tasks to the SRCTREECOVEREDTASKS list. There is no need for devtool to
duplicate this code and override what the kernel-yocto.bbclass already
does.
devtool modify generates a linux-yocto.6.6.bbappend
From: Adrian Freihofer
How to reproduce:
- UBOOT_CONFIG must be used. With UBOOT_MACHINE it works fine.
A simple example based on oe-core is to modify the
beaglebone-yocto.conf file like this:
-UBOOT_MACHINE = "am335x_evm_defconfig"
+UBOOT_CONFIG = "foo"
+UBOOT_CONFIG[foo] = "am335x_evm
From: Adrian Freihofer
Drop the redundant generation of the do_configure:append section for the
kernel. The same append is generated twice:
if bb.data.inherits_class('kernel', rd):
f.write('\ndo_configure:append() {\n'
'cp ${B}/.config ${S}/.config.baseline\n'
'ln -sfT ${B}/.
From: Alexander Sverdlin
mkimage doesn't fail if it is not able to sign FIT nodes.
This may lead to unbootable images in secure boot configurations.
Make signing failures fatal by parsing the mkimage output.
Signed-off-by: Alexander Sverdlin
---
Changes in v3:
- bbfatag_log -> bberror + bbfatal
Hi Bruce,
thanks for the quick review!
On Mon, 2024-09-02 at 09:52 -0400, Bruce Ashfield wrote:
> > From: Alexander Sverdlin
> >
> > mkimage doesn't fail if it is not able to sign FIT nodes.
> > This may lead to unbootable images in secure boot configurations.
> > Make signing failures fatal by
* and add -fmacro-prefix-map as well
* the default STAGING_DIR_NATIVE starts with STAGING_DIR_HOST and the
only difference is '-native' suffix at the end
* this can lead into replacing STAGING_DIR_NATIVE path with just -native
if STAGING_DIR_HOST is listed in DEBUG_PREFIX_MAP before STAGING_D
On Mon, 2 Sept 2024 at 16:15, Mikko Rapeli wrote:
> So, this is a wic image format specific re-implementation of systemd ukify.py
> script.
> Calling not systemd ukify.py but objcopy directly. No control over kernel
> command
> line, but could possible be added with simple patch. I don't see ho
Hi,
On Mon, Sep 02, 2024 at 04:15:21PM +0300, Mikko Rapeli via
lists.openembedded.org wrote:
> On Mon, Sep 02, 2024 at 03:03:45PM +0200, Alexander Kanavin wrote:
> > On Mon, 2 Sept 2024 at 14:25, Mikko Rapeli wrote:
> > > I've checked and I have not found matching examples. We have everything
>
On Mon, Sep 2, 2024 at 7:46 AM A. Sverdlin
wrote:
> From: Alexander Sverdlin
>
> mkimage doesn't fail if it is not able to sign FIT nodes.
> This may lead to unbootable images in secure boot configurations.
> Make signing failures fatal by parsing the mkimage output.
>
> Signed-off-by: Alexander
NVD's certificate has expired. At this moment some servers have the new
one, some the old one. Expect strange issues.
Mata
On Mon, Sep 2, 2024 at 3:25 PM Richard Purdie via lists.yoctoproject.org
wrote:
> On Sun, 2024-09-01 at 01:18 -1000, Steve Sakoman via
> lists.yoctoproject.org wrote:
> > F
On Sun, 2024-09-01 at 01:18 -1000, Steve Sakoman via lists.yoctoproject.org
wrote:
> Full list: Found 0 unpatched CVEs
Much as I wish that were true... :/
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#204103):
https://lists.op
Hi,
On Mon, Sep 02, 2024 at 03:03:45PM +0200, Alexander Kanavin wrote:
> On Mon, 2 Sept 2024 at 14:25, Mikko Rapeli wrote:
> > I've checked and I have not found matching examples. We have everything
> > working
> > for UEFI secure boot for multiple ARM64 boards and qemu, including oeqa
> > runt
On Mon, 2 Sept 2024 at 14:25, Mikko Rapeli wrote:
> I've checked and I have not found matching examples. We have everything
> working
> for UEFI secure boot for multiple ARM64 boards and qemu, including oeqa
> runtime tests.
> Currently the qemu side changes to support UEFI secure boot are queue
Hi,
On Mon, Sep 02, 2024 at 02:01:31PM +0200, Alexander Kanavin wrote:
> On Mon 2. Sep 2024 at 13.23, Mikko Rapeli wrote:
>
> > Hi,
> >
> > On Mon, Sep 02, 2024 at 01:11:27PM +0200, Alexander Kanavin wrote:
> > > Should this also have a wic based selftest or some other way to ensure it
> > > wor
On Mon, 2024-09-02 at 11:31 +0100, Pedro Ferreira wrote:
> From: Richard Purdie
>
> This was deprecated with the introduction of postfunc support for
> tasks
> in general and only used by buildhistory. Now that usage has been
> removed,
> drop the code from sstate.bbclass. Any other users should
On Mon 2. Sep 2024 at 13.23, Mikko Rapeli wrote:
> Hi,
>
> On Mon, Sep 02, 2024 at 01:11:27PM +0200, Alexander Kanavin wrote:
> > Should this also have a wic based selftest or some other way to ensure it
> > works?
>
> Yes, but that depends on the UEFI / Arm System Ready compatible firmware.
>
>
From: Alexander Sverdlin
mkimage doesn't fail if it is not able to sign FIT nodes.
This may lead to unbootable images in secure boot configurations.
Make signing failures fatal by parsing the mkimage output.
Signed-off-by: Alexander Sverdlin
---
Changes in v2:
- bbfatal -> bbfatal_log
meta/cl
Hi,
On Mon, Sep 02, 2024 at 01:11:27PM +0200, Alexander Kanavin wrote:
> Should this also have a wic based selftest or some other way to ensure it
> works?
Yes, but that depends on the UEFI / Arm System Ready compatible firmware.
For qemu, this can be setup using meta-arm and qemuarm64-secureboo
Should this also have a wic based selftest or some other way to ensure it
works?
Alex
On Mon 2. Sep 2024 at 12.58, Mikko Rapeli via lists.openembedded.org
wrote:
> From: Michelle Lin
>
> This class calls systemd ukify tool, which will combine
> kernel/initrd/stub components to build the UKI. T
The contents of the COPYING file included in the current source code
package match those of GPL-3.0-only license, which seems to have been
the case since 2008 commit
http://git.savannah.gnu.org/gitweb/?p=dejagnu.git;a=commitdiff;h=9bebe7b9bfb9b02e5e4d86ad74e8ce3eb32a36b9;hp=50fbdd118dba066e201c73a8
On Mon, 2 Sep 2024, Richard Purdie wrote:
> On Mon, 2024-09-02 at 06:39 -0400, Robert P. J. Day via
> lists.openembedded.org wrote:
> >
> > i'm sure i've overlooked something silly, but in building a
> > qemuarm64 image to demo ptest to some colleagues, poky by default sets
> > the "ptest" DIST
From: Michelle Lin
This class calls systemd ukify tool, which will combine
kernel/initrd/stub components to build the UKI. To sign the UKI
(i.e. SecureBoot), the keys/cert files can be specified
in a configuration file or UEFI binary signing can be done
via separate steps, see qemuarm64-secureboo
It's needed to run the ukify script.
Signed-off-by: Mikko Rapeli
---
meta/recipes-core/systemd/systemd-boot-native_256.5.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-core/systemd/systemd-boot-native_256.5.bb
b/meta/recipes-core/systemd/systemd-boot-native_256.5.bb
index
These changes enable building systemd uki images which combine
kernel, kernel command line, initrd and possibly signatures to
a single UEFI binary. This binary can be booted with UEFI firmware
and systemd-boot. No grub is needed and UEFI firmware and/or
systemd-boot provide possibilities for boot m
On Mon, 2024-09-02 at 06:39 -0400, Robert P. J. Day via lists.openembedded.org
wrote:
>
> i'm sure i've overlooked something silly, but in building a
> qemuarm64 image to demo ptest to some colleagues, poky by default sets
> the "ptest" DISTRO_FEATURES setting so all of the corresponding ptest
i'm sure i've overlooked something silly, but in building a
qemuarm64 image to demo ptest to some colleagues, poky by default sets
the "ptest" DISTRO_FEATURES setting so all of the corresponding ptest
packages are *built*, but when adding:
EXTRA_IMAGE_FEATURES += "ptest-pkgs"
only *some* of
On Mon Sep 2, 2024 at 11:41 AM CEST, Mikko Rapeli wrote:
> From: Michelle Lin
>
> This class calls systemd ukify tool, which will combine
> kernel/initrd/stub components to build the UKI. To sign the UKI
> (i.e. SecureBoot), the keys/cert files can be specified
> in a configuration file or UEFI bi
On Mon Sep 2, 2024 at 12:17 PM CEST, Alexander Kanavin wrote:
> Wait. Isn't this ukify.py thingy already provided from
> systemd-boot-native recipe?
Yes. It was added while I did this change as part of a PoC ~a year ago.
I am not a huge fan of it having landed in systemd-boot-native. I
think ther
Hi,
On Mon, Sep 02, 2024 at 01:27:05PM +0300, Mikko Rapeli via
lists.openembedded.org wrote:
> Hi,
>
> On Mon, Sep 02, 2024 at 12:15:02PM +0200, Alexander Kanavin wrote:
> > Also, can't this be supplied with DEPENDS? Adding to HOSTTOOLS to
> > cater to needs of a single recipe is not a good thin
On Mon, 2 Sept 2024 at 12:27, Mikko Rapeli wrote:
> On Debian/Ubuntu getent is part of libc-bin package which is marked
> essential so installed basically everywhere by default. The systemd
> side meson build script was failing without it. I can try to check
> if there some config etc way to disab
This fix will ensure that, when we activate feature
`BUILDHISTORY_RESET`, files marked to keep on feature
`BUILDHISTORY_PRESERVE` will indeed exist is buildhistory
final path since they are moved to buildhistory/old but
not restored at any point.
Signed-off-by: Pedro Ferreira
Signed-off-by: Richa
From: Richard Purdie
This was deprecated with the introduction of postfunc support for tasks
in general and only used by buildhistory. Now that usage has been removed,
drop the code from sstate.bbclass. Any other users should be able to use
postfuncs too.
Signed-off-by: Richard Purdie
---
meta
The directory that buildhistory_list_pkg_files writes to during do_package
is created by do_packagedata so a clean buildhistory doesn't have
files-in-package written during the first build since packagedata happens
after do_package.
Ensure the output package folder is created to avoid missing
file
From: Richard Purdie
We planned to drop SSTATEPOSTINSTFUNC some time ago with the introduction of
postfuncs. Finally get around to doing that which should make the buildhistory
code a little more readable.
Unfortunately ordering the buildhistory function calls after the sstate ones is
difficult
Hi,
On Mon, Sep 02, 2024 at 12:17:53PM +0200, Alexander Kanavin wrote:
> Wait. Isn't this ukify.py thingy already provided from
> systemd-boot-native recipe?
Oh, it is. I've somehow missed this. Will switch over to it.
Cheers,
-Mikko
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent
Hi,
On Mon, Sep 02, 2024 at 12:15:02PM +0200, Alexander Kanavin wrote:
> Also, can't this be supplied with DEPENDS? Adding to HOSTTOOLS to
> cater to needs of a single recipe is not a good thing.
On Debian/Ubuntu getent is part of libc-bin package which is marked
essential so installed basically
The directory that buildhistory_list_pkg_files writes to during do_package
is created by do_packagedata so a clean buildhistory doesn't have
files-in-package written during the first build since packagedata happens
after do_package.
Ensure the output package folder is created to avoid missing
file
From: Richard Purdie
This was deprecated with the introduction of postfunc support for tasks
in general and only used by buildhistory. Now that usage has been removed,
drop the code from sstate.bbclass. Any other users should be able to use
postfuncs too.
Signed-off-by: Richard Purdie
(cherry p
This fix will ensure that, when we activate feature
`BUILDHISTORY_RESET`, files marked to keep on feature
`BUILDHISTORY_PRESERVE` will indeed exist is buildhistory
final path since they are moved to buildhistory/old but
not restored at any point.
Signed-off-by: Pedro Ferreira
Signed-off-by: Richa
From: Richard Purdie
We planned to drop SSTATEPOSTINSTFUNC some time ago with the introduction of
postfuncs. Finally get around to doing that which should make the buildhistory
code a little more readable.
Unfortunately ordering the buildhistory function calls after the sstate ones is
difficult
Wait. Isn't this ukify.py thingy already provided from
systemd-boot-native recipe?
Alex
On Mon, 2 Sept 2024 at 12:06, Mikko Rapeli via lists.openembedded.org
wrote:
>
> Hi,
>
> On Mon, Sep 02, 2024 at 10:59:22AM +0100, Richard Purdie wrote:
> > This will fail in CI as there is now maintainers fi
Also, can't this be supplied with DEPENDS? Adding to HOSTTOOLS to
cater to needs of a single recipe is not a good thing.
Alex
On Mon, 2 Sept 2024 at 12:10, Peter Kjellerstedt via
lists.openembedded.org
wrote:
>
> > -Original Message-
> > From: openembedded-core@lists.openembedded.org
>
Hi,
On Mon, Sep 02, 2024 at 10:09:54AM +, Peter Kjellerstedt wrote:
> > -Original Message-
> > From: openembedded-core@lists.openembedded.org
> > On Behalf Of Mikko Rapeli
> > Sent: den 2 september 2024 11:41
> > To: openembedded-core@lists.openembedded.org
> > Cc: Mikko Rapeli
> >
> -Original Message-
> From: openembedded-core@lists.openembedded.org
> On Behalf Of Mikko Rapeli
> Sent: den 2 september 2024 11:41
> To: openembedded-core@lists.openembedded.org
> Cc: Mikko Rapeli
> Subject: [OE-core] [PATCH 2/3] bitbake.conf: add getopt to HOSTTOOLS
You are adding ge
Hi,
On Mon, Sep 02, 2024 at 10:59:22AM +0100, Richard Purdie wrote:
> This will fail in CI as there is now maintainers file entry...
Chen, since you are systemd maintainer, would you mind if I add
systemd-tools for you too? It's only the ukify python script
currently for native use cases at build
On Mon, 2024-09-02 at 12:41 +0300, Mikko Rapeli via
lists.openembedded.org wrote:
> From: Erik Schilling
>
> Provides systemd-tools-native recipe for ukify.py tooling.
> Avoids full systemd native build which is not needed.
>
> Signed-off-by: Mikko Rapeli
> ---
> .../systemd/systemd-tools_256.
Needed by systemd-tools-native
Signed-off-by: Mikko Rapeli
---
meta/conf/bitbake.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index d8252c5b82..a8c630e7f8 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
From: Michelle Lin
This class calls systemd ukify tool, which will combine
kernel/initrd/stub components to build the UKI. To sign the UKI
(i.e. SecureBoot), the keys/cert files can be specified
in a configuration file or UEFI binary signing can be done
via separate steps, see qemuarm64-secureboo
From: Erik Schilling
Provides systemd-tools-native recipe for ukify.py tooling.
Avoids full systemd native build which is not needed.
Signed-off-by: Mikko Rapeli
---
.../systemd/systemd-tools_256.5.bb| 41 +++
1 file changed, 41 insertions(+)
create mode 100644 met
These changes enable building systemd uki images which combine
kernel, kernel command line, initrd and possibly signatures to
a single UEFI binary. This binary can be booted with UEFI firmware
and systemd-boot. No grub is needed and UEFI firmware and/or
systemd-boot provide possibilities for boot m
On Mon, 2024-09-02 at 00:39 -0700, Hemraj, Deepthi via lists.openembedded.org
wrote:
> From: Deepthi Hemraj
>
> [YOCTO #15338]
> Enabled ptest integration in gcc-sanitizers.inc to facilitate the proper
> testing and execution of address sanitizer (ASan)
>
> Defined the do_check task to execute
* in builds with zip in HOSTTOOLS mc fails with:
ERROR: mc-4.8.31-r0 do_package_qa: QA Issue: File
/usr/libexec/mc/extfs.d/uzip in package mc-helpers-perl contains reference to
TMPDIR [buildpaths]
and it's because of the path to zip:
mc/4.8.31/package $ grep -R styhead .
./usr/libexec/mc/
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/gcc-sanitizers-Add-ptest-support-for-AddressSanitizer-tests.patch
FAIL: test Signed-off-by presence: A patch file h
From: Deepthi Hemraj
[YOCTO #15338]
Enabled ptest integration in gcc-sanitizers.inc to facilitate the proper
testing and execution of address sanitizer (ASan)
Defined the do_check task to execute ASan tests with proper environment setup
and updated do_install_ptest_base to copy ASan test execu
62 matches
Mail list logo
