Re: [OE-core] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.4.1.rc1)

Hi everyone, Intel and WR YP QA is planning for QA execution for YP build yocto-3.4.1.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. MinnowTurbot 32-bit 2. Coffee Lake 3.

[OE-core] [hardknott][PATCH 14/14] cups: Fix missing installation of cups sysv init scripts

From: Claus Stovgaard The packageconfig needs to be --disable-systemd as documented in configure file for cups. With the current value "--without-systemd" the SYSTEM_DIR variable ends up being set to "no" It is caused by the --without-* section in configure file resulting in eval

[OE-core] [hardknott][PATCH 13/14] python3: update to 3.9.7

From: Oleksandr Kravchuk Signed-off-by: Oleksandr Kravchuk Signed-off-by: Alexandre Belloni (cherry picked from commit 9612bb0639c13571e661f208aa7b28789953d9ec) Signed-off-by: Anuj Mittal --- .../python/{python3_3.9.6.bb => python3_3.9.7.bb} | 2 +- 1 file changed, 1

[OE-core] [hardknott][PATCH 12/14] python3: upgrade 3.9.5 -> 3.9.6

From: zhengruoqin 0001-Makefile-fix-Issue36464-parallel-build-race-problem.patch removed since it is included in 3.9.6 Signed-off-by: Zheng Ruoqin Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 1a12d978f2046fc5d3abc96db3753e378f29ecae)

[OE-core] [hardknott][PATCH 11/14] os-release: Add DISTRO_CODENAME as vardeps for do_compile

From: Daniel Gomez DISTRO_CODENAME is part of VERSION variable but not used as dependency for do_compile task. Append it to the vardeps list to rebuild in case it changes. Signed-off-by: Daniel Gomez Signed-off-by: Richard Purdie (cherry picked from commit

[OE-core] [hardknott][PATCH 10/14] linux-yocto/5.10: update to v5.10.79

From: Bruce Ashfield Updating linux-yocto/5.10 to the latest korg -stable release that comprises the following commits: bd816c278316 Linux 5.10.79 62424fe4c2cf rsi: fix control-message timeout 8971158af1e0 media: staging/intel-ipu3: css: Fix wrong size comparison imgu_css_fw_init

[OE-core] [hardknott][PATCH 03/14] linux-yocto/5.4: update to v5.4.156

From: Bruce Ashfield Updating linux-yocto/5.4 to the latest korg -stable release that comprises the following commits: 89b6869b942b Linux 5.4.156 7cdcaa7c765b pinctrl: stm32: use valid pin identifier in stm32_pinctrl_resume() a9c4e246f7c3 ARM: 9122/1: select HAVE_FUTEX_CMPXCHG

[OE-core] [hardknott][PATCH 08/14] gmp: fix CVE-2021-43618

From: Ross Burton Signed-off-by: Ross Burton Signed-off-by: Richard Purdie (cherry picked from commit fb3b9a7f668a6ffd56a99e1e8b83cdbad2a4bc66) Signed-off-by: Anuj Mittal --- .../gmp/gmp/cve-2021-43618.patch | 27 +++ meta/recipes-support/gmp/gmp_6.2.1.bb

[OE-core] [hardknott][PATCH 09/14] glibc: Fix i586/c3 support

From: Richard Purdie CET can't be enabled on i586 or c3 for x86, adjust the configuration accordingly to fix those builds. [YOCTO #14632] Signed-off-by: Richard Purdie (cherry picked from commit 26e4fed594daefb6923c50171360f925c4822683) Signed-off-by: Anuj Mittal ---

[OE-core] [hardknott][PATCH 07/14] wic: use shutil.which

From: Mingli Yu Use shutil.which to find the executable instead to silence the below warning: $ cat tmp/work/intel_x86_64-poky-linux/core-image-base/1.0-r5/temp/log.do_image_wic [snip] DEBUG: Executing shell function do_image_wic /path/layers/oe-core/scripts/wic:27: DeprecationWarning: The

[OE-core] [hardknott][PATCH 06/14] uninative: Add version to uninative tarball name

From: Richard Purdie uninative works via hashes and doesn't need the version in the tarball name but it does make things easier to inspect in DL_DIR. There were reasons such as ease of publication of the build tarballs but we can handle those differently now and the signature issues from the

[OE-core] [hardknott][PATCH 05/14] go: upgrade 1.16.8 -> 1.16.10

From: Pavel Zhukov The release includes fixes for CVE-2021-41771 and CVE-2021-41772 Signed-off-by: Pavel Zhukov Signed-off-by: Richard Purdie This release also contains a fix for CVE-2021-38297 and the changes are minor, so backport the uprev rather than manually backporting individual

[OE-core] [hardknott][PATCH 04/14] linux-yocto/5.4: update to v5.4.158

From: Bruce Ashfield Updating linux-yocto/5.4 to the latest korg -stable release that comprises the following commits: c65356f0f726 Linux 5.4.158 e31d51f8a41f ARM: 9120/1: Revert "amba: make use of -1 IRQs warn" 960b1fdfc39a Revert "drm/ttm: fix memleak in ttm_transfered_destroy"

[OE-core] [hardknott][PATCH 02/14] linux-yocto/5.4: update to v5.4.155

From: Bruce Ashfield Updating linux-yocto/5.4 to the latest korg -stable release that comprises the following commits: 4f508aa9dd3b Linux 5.4.155 32d2ce0b9499 ionic: don't remove netdev->dev_addr when syncing uc list abaf8e8b9081 r8152: select CRC32 and

[OE-core] [hardknott][PATCH 01/14] linux-yocto/5.4: update to v5.4.154

From: Bruce Ashfield Updating linux-yocto/5.4 to the latest korg -stable release that comprises the following commits: ce061ef43f1d Linux 5.4.154 291a48871e51 sched: Always inline is_percpu_thread() 3e105ecc4ab7 scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported"

[OE-core] [hardknott][PATCH 00/14] Review request

Next set of changes for hardknott. Please review. No problems seen while testing on autobuilder except for an intermittent qemu bootup failure. https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2975 Thanks, Anuj The following changes since commit

[OE-core] [PATCH] linux-yocto-dev: Make -dev kernel work for a fixed revision

By default the -dev kernel uses the "AUTOREV" to pull in the branch head as the revision. Some of our BSPs are based on the -dev kernel and we choose to nail down the kernel to a specific revision when releasing our product by using some setting like below: PREFERRED_PROVIDER_virtual/kernel =

Re: [OE-core] [RFC] meson needs a pkg-config wrapper script

Based on my testing, if PKG_CONFIG_SYSROOT_DIR is set or not makes zero difference on the outcome. I suspect this is related to how pkg-config is launched by meson. Looking at the meson source tree, in all ci/test cross compile scenarios they reference a pkg-config wrapper. No cross compile

[OE-core] [RFC PATCH v2 2/2] Improve native reproducibility in recipes

Avoid encoding build-specific paths in the resulting binaries. Signed-off-by: Jacob Kroon --- ...sysroot-and-debug-prefix-map-from-co.patch | 78 --- .../openssl/openssl/strip-buildinfo.patch | 13 .../openssl/openssl_3.0.0.bb | 10 +--

[OE-core] [RFC PATCH v2 1/2] bitbake.conf: Pad rpath and remove build ID in native binaries

Try to make sure that the RUNTIME dynamic entry size is the same for all binaries produced with the native compiler. This is necessary in order to produce identical binaries when using differently sized buildpaths. I've tried using only patchelf, and keeping the linker flags as they are, but I am

[OE-core] [RFC PATCH v2 0/2] Improve native/cross reproducibility

This patch series is not intended for merge. I only send it out to highlight where the problems are and to get some discussion going on how/if we want to improve the sitation. This is a patch series that tries to improve the reproducibility of the native/cross binaries when building in different

Re: [OE-core] [PATCH v2 2/2] vim: set PACKAGECONFIG idiomatically

On Tue, Nov 30, 2021 at 1:20 PM Ross Burton wrote: > > On Tue, 30 Nov 2021 at 19:32, Andre McCurdy wrote: > > This isn't equivalent - it will cause a change in behaviour for anyone > > using PACKAGECONFIG += "foo" from a .bbappend. > > Correct, but this is likely the only recipe in the greater

Re: [OE-core] [PATCH v2 2/2] vim: set PACKAGECONFIG idiomatically

On Tue, 30 Nov 2021 at 19:32, Andre McCurdy wrote: > This isn't equivalent - it will cause a change in behaviour for anyone > using PACKAGECONFIG += "foo" from a .bbappend. Correct, but this is likely the only recipe in the greater ecosystem which has this behaviour, so I'm not that bothered to

Re: [OE-core] [RFC] meson needs a pkg-config wrapper script

On Tue, 30 Nov 2021 at 17:20, Joel Winarske wrote: > PKG_CONFIG_SYSROOT_DIR behaves like a simple string prepend to all package > config variable queries. So if you want to determine the absolute path of a > variable in .pc you set PKG_CONFIG_SYSROOT_DIR and make your query. > Currently this

[OE-core] Yocto Project Status WW48`21

Current Dev Position: YP 3.5 M1 Next Deadline: 6th Dec. 2021 YP 3.5 M1 build Next Team Meetings: * Bug Triage meeting Thursday Dec. 9th at 7:30am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) *

Re: [OE-core] [RFC] meson needs a pkg-config wrapper script

On Tue, 30 Nov 2021 at 21:00, Joel Winarske wrote: > Yes, if the sys_root key value in meson.cross is present > PKG_CONFIG_SYSROOT_DIR gets set. Honister patch I confirmed with: > > https://github.com/jwinarske/manifests/blob/honister/rpi64/0001-Add-sys_root-to-properties-section.patch > > The

Re: [OE-core] [RFC] meson needs a pkg-config wrapper script

Also all of the above requires this change: https://github.com/KhronosGroup/Vulkan-Loader/pull/756 On Tue, Nov 30, 2021 at 12:00 PM Joel Winarske wrote: > Yes, if the sys_root key value in meson.cross is present > PKG_CONFIG_SYSROOT_DIR gets set. Honister patch I confirmed with: > >

Re: [OE-core] [RFC] meson needs a pkg-config wrapper script

Yes, if the sys_root key value in meson.cross is present PKG_CONFIG_SYSROOT_DIR gets set. Honister patch I confirmed with: https://github.com/jwinarske/manifests/blob/honister/rpi64/0001-Add-sys_root-to-properties-section.patch The issue is that meson doesn't pass PKG_CONFIG_SYSROOT_DIR to the

Re: [OE-core] [RFC] meson needs a pkg-config wrapper script

I am seeing in mesonbuild/dependencies/pkgconfig.py sysroot = environment.properties[for_machine].get_sys_root() if sysroot: env['PKG_CONFIG_SYSROOT_DIR'] = sysroo So we probably need to ensure this 'sys_root' is correctly set, and then things will simply work? Alex

Re: [OE-core] [PATCH v2 2/2] vim: set PACKAGECONFIG idiomatically

On Tue, Nov 30, 2021 at 8:53 AM Ross Burton wrote: > > Don't set an empty default value and them immediately assign to it. > > Signed-off-by: Ross Burton > --- > meta/recipes-support/vim/vim.inc | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > > diff --git

Re: [OE-core] [RFC] meson needs a pkg-config wrapper script

https://github.com/vkmark/vkmark/blob/master/src/meson.build#L9 On Tue, Nov 30, 2021 at 10:53 AM Alexander Kanavin wrote: > I do not quite understand the use case. What is being done with the full > path to the header? > > Alex > > On Tue, 30 Nov 2021 at 19:26, Joel Winarske > wrote: > >> This

Re: [OE-core] [RFC] meson needs a pkg-config wrapper script

I do not quite understand the use case. What is being done with the full path to the header? Alex On Tue, 30 Nov 2021 at 19:26, Joel Winarske wrote: > This pattern works to get the absolute path of the header: > > Yocto > > EXTRA_OEMESON += "--prefix ${STAGING_DIR_TARGET}/usr" > > Meson >

Re: [OE-core] [RFC] meson needs a pkg-config wrapper script

This pattern works to get the absolute path of the header: Yocto EXTRA_OEMESON += "--prefix ${STAGING_DIR_TARGET}/usr" Meson vulkan_dep = dependency('vulkan') vulkan_hpp = join_paths([ vulkan_dep.get_pkgconfig_variable('includedir', define_variable: ['prefix',

Re: [OE-core] [RFC] meson needs a pkg-config wrapper script

On Tue, 30 Nov 2021 at 18:20, Joel Winarske wrote: > Meson does not expose PKG_CONFIG_SYSROOT_DIR to the pkg-config process. > > Currently meson.cross as generated in meson.bbclass points directly to the > pkg-config executable (no wrapper script). > > PKG_CONFIG_SYSROOT_DIR behaves like a

[OE-core] [PATCH] libtool: Fix status format in patch header

Insert a space After 'Backport' Signed-off-by: Khem Raj --- .../libtool/ARFLAGS-use-cr-instead-of-cru-by-default.patch | 2 +- .../libtool/libtool/libool.m4-add-ARFLAGS-variable.patch| 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git

[OE-core] [RFC] meson needs a pkg-config wrapper script

Meson does not expose PKG_CONFIG_SYSROOT_DIR to the pkg-config process. Currently meson.cross as generated in meson.bbclass points directly to the pkg-config executable (no wrapper script). PKG_CONFIG_SYSROOT_DIR behaves like a simple string prepend to all package config variable queries. So if

[OE-core] [PATCH v2 2/2] vim: set PACKAGECONFIG idiomatically

Don't set an empty default value and them immediately assign to it. Signed-off-by: Ross Burton --- meta/recipes-support/vim/vim.inc | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/meta/recipes-support/vim/vim.inc b/meta/recipes-support/vim/vim.inc index

[OE-core] [PATCH v2 1/2] vim: fix CVE-2021-3968 and CVE-2021-3973

Backport a fix for -3972, and whitelist -3968: it isn't valid as it fixes a bug which was introduced after 8.2. Signed-off-by: Ross Burton --- ...rash-when-using-CTRL-W-f-without-fin.patch | 92 +++ meta/recipes-support/vim/vim.inc | 4 + 2 files changed, 96

Re: [OE-core] vulkan-loader

[Readable version] https://github.com/KhronosGroup/Vulkan-Loader/commit/3c1ad4b0d54875ff0899b77a92aeda53ca236f27 Before: $ pkg-config --print-errors --define-variable=prefix=/opt --variable=includedir vulkan /usr/include After: $ pkg-config --print-errors --define-variable=prefix=/opt

Re: [OE-core] [PATCH 0/6] Pull request (cover letter only)

The patchset is now under testing: https://git.yoctoproject.org/poky/log/?h=master-next If there are issues, you'll hear about them, otherwise the patches will quietly land in master :) Alex On Tue, 30 Nov 2021 at 09:14, Vyacheslav Yurkov wrote: > Just pinging to check if anyone had a chance

Re: [OE-core] [meta][dunfell][PATCH] glib-2.0: Add security fixes

Steve, I have just sent a patch v2 with added all missing regression patchsets as well as patch fuzz removed from CVE-2021-28153-4.patch. Please check it and let me know if anything else is needed for the same. Thanks, Best Regards, Ranjitsinh Rathod Technical Leader | | KPIT Technologies

[OE-core] [meta][dunfell][PATCH v2] glib-2.0: Add security fixes

From: Neetika Singh Add patches for below CVE issues: CVE-2021-27218 CVE-2021-27219 CVE-2021-28153 Link: https://mirrors.ocf.berkeley.edu/ubuntu/pool/main/g/glib2.0/glib2.0_2.64.6-1~ubuntu20.04.3.debian.tar.xz Also, add regression patchs for CVE-2021-27219. CVE-2021-27219-reg1-3.patch is not

Re: [OE-core] [meta][dunfell][PATCH] glib-2.0: Add security fixes

On Mon, Nov 29, 2021 at 9:12 PM Ranjitsinh Rathod wrote: > > Adding missing patches and will resent it. While you are at it you might also want to check CVE-2021-28153-4.patch, I had to tweak it slightly to get it to apply cleanly (i.e. without a fuzz warning). Steve > > Thanks, > Ranjitsinh

Re: [OE-core] Not able to install chrony on zeus

Thanks Khem Raj, Found jamvm class with update-alternative option. jamvm.inc\jamvm\recipes-core - meta-java - Layer containing recipes for OpenJDK and other open source Java- (yoctoproject.org) ( https://git.yoctoproject.org/meta-java/tree/recipes-core/jamvm/jamvm.inc?h=master ) I see chrony

Re: [OE-core] vulkan-loader

https://github.com/KhronosGroup/Vulkan-Loader/commit/3c1ad4b0d54875ff0899b77a92aeda53ca236f27 Before: $ pkg-config --print-errors --define-variable=prefix=/opt --variable=includedir vulkan /usr/include After: $ pkg-config --print-errors --define-variable=prefix=/opt --variable=includedir vulkan

[OE-core] [dunfell][PATCH] cmake: FindGTest: Add target for gmock library

`googlemock` has been absorbed into the [googletest](https://github.com/google/googletest) project and is built and installed from the same source tree. `googletest` has provided a CMake Config-file Package starting with GTest 1.8.1. `find_package(GTest ...)` by default dispatches first to CMake

Re: [OE-core] [PATCH 0/6] Pull request (cover letter only)

Just pinging to check if anyone had a chance to take a look at it Thanks, Vyacheslav On 19.11.2021 07:15, Vyacheslav Yurkov via lists.openembedded.org wrote: This is a V1 of overlayfs-etc image feature implementation, that allows to setup the whole /etc under overlayfs. Please review and merge