Re: [OE-core] [PATCH 1/4] recipetool: Set master branch only as fallback

Hi Richard, Am 07.12.2021 um 16:45 schrieb Richard Purdie: On Mon, 2021-12-06 at 09:04 +0100, Stefan Herbrechtsmeier wrote: From: Stefan Herbrechtsmeier The commit 'meta/scripts: Manual git url branch additions (dc53fe75cc)' sets the branch= parameter too early to master and thereby breaks

[OE-core] [PATCH] libhandy: add hdy-enums-private.h

From: Mingli Yu After the commit(8157ecc Separate public and private enums) introduced, there comes a race as below: | In file included from ../git/src/hdy-settings.c:11: | ../git/src/hdy-settings-private.h:16:10: fatal error: hdy-enums-private.h: No such file or directory |16 | #include

[OE-core] [PATCH] cmake: upgrade 3.22.0 -> 3.22.1

From: Changqing Li This upgrade include a bug fix: Refer: https://gitlab.kitware.com/cmake/cmake/-/issues/22963 https://gitlab.kitware.com/cmake/cmake/-/commit/643fc46bdc13dd57584d5d77eee30a99308ba896 Signed-off-by: Changqing Li --- .../cmake/{cmake-native_3.22.0.bb => cmake-native_3.22.1.bb}

Re: [OE-core] [PATCH] Build libstd-rs in release mode to compile mozjs

On 2021-12-06 3:20 a.m., Alexander Kanavin wrote: On Mon, 6 Dec 2021 at 06:45, pgowda > wrote: When mozjs in firefox is built with DEBUG_BUILD = "1" in local.conf, it will fail with the following error:  

Re: [OE-core] [PATCH 05/16] rustfmt: remove the recipe

Fine with me. Even building rustfmt seems to require the nightly toolchain so let's drop it for now. Randy On Tue., Dec. 7, 2021, 11:01 Khem Raj, wrote: > On Tue, Dec 7, 2021 at 5:07 AM Alexander Kanavin > wrote: > > > > There has been a discussion on the merits of keeping rustfmt in core,

Re: [OE-core] [PATCH 1/3] mesa: Fix broadcom vulkan driver build on 32bit arches with 64bit time_t

On Tue, Dec 7, 2021 at 11:36 AM Alexander Kanavin wrote: > > No more 'Pending' please :) mesa has a gitlab, so it's trivial to submit the > patch. Good point, I have it already under review, I should have updated the status here, v2 has it updated. > > Alex > > On Tue, 7 Dec 2021 at 20:25,

Re: [OE-core] [PATCH v2] mesa: Fix broadcom vulkan driver build on 32bit arches with 64bit time_t

Thanks :) Alex On Tue, 7 Dec 2021 at 21:14, Khem Raj wrote: > Signed-off-by: Khem Raj > --- > v2: Update patch status > > ...unt-for-64bit-time_t-on-32bit-arches.patch | 41 +++ > meta/recipes-graphics/mesa/mesa.inc | 1 + > 2 files changed, 42 insertions(+) >

[OE-core] [PATCH] mesa: Define broadcom packageconfig knob

Fixes ERROR: mesa-2_21.3.0-r0 do_configure: QA Issue: mesa: invalid PACKAGECONFIG: broadcom [invalid-packageconfig] Signed-off-by: Khem Raj --- meta/recipes-graphics/mesa/mesa.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-graphics/mesa/mesa.inc

[OE-core] [PATCH v2] mesa: Fix broadcom vulkan driver build on 32bit arches with 64bit time_t

Signed-off-by: Khem Raj --- v2: Update patch status ...unt-for-64bit-time_t-on-32bit-arches.patch | 41 +++ meta/recipes-graphics/mesa/mesa.inc | 1 + 2 files changed, 42 insertions(+) create mode 100644

Re: [OE-core] [PATCH] pango: upgrade 1.48.10 -> 1.50.0

Upstream seems to have merged a bunch of related fixes, so let's wait for 1.50.1: https://gitlab.gnome.org/GNOME/pango/-/commits/main Alex On Tue, 7 Dec 2021 at 17:52, Ross Burton wrote: > And > https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/2624/steps/12/logs/stdio > , > so

Re: [OE-core] [PATCH 1/3] mesa: Fix broadcom vulkan driver build on 32bit arches with 64bit time_t

No more 'Pending' please :) mesa has a gitlab, so it's trivial to submit the patch. Alex On Tue, 7 Dec 2021 at 20:25, Khem Raj wrote: > Signed-off-by: Khem Raj > --- > ...unt-for-64bit-time_t-on-32bit-arches.patch | 41 +++ > meta/recipes-graphics/mesa/mesa.inc | 1

[OE-core] [PATCH 3/3] binutils: Drop patch to wider sh regexp

This was needed during uclibc days and remnants have lingered on. Remove this patch Signed-off-by: Khem Raj --- .../binutils/binutils-2.37.inc| 1 - ...iden-the-regexp-for-SH-architectures.patch | 41 --- 2 files changed, 42 deletions(-) delete mode 100644

[OE-core] [PATCH 2/3] gdb: Drop sh4 support patch

This patch needs to be upstreamed, its not clear if it still works. Signed-off-by: Khem Raj --- meta/recipes-devtools/gdb/gdb-11.1.inc| 1 - ...port-for-Renesas-SH-sh4-architecture.patch | 914 -- 2 files changed, 915 deletions(-) delete mode 100644

[OE-core] [PATCH 1/3] mesa: Fix broadcom vulkan driver build on 32bit arches with 64bit time_t

Signed-off-by: Khem Raj --- ...unt-for-64bit-time_t-on-32bit-arches.patch | 41 +++ meta/recipes-graphics/mesa/mesa.inc | 1 + 2 files changed, 42 insertions(+) create mode 100644

Re: [OE-core] [PATCH 15/16] ruby: update 3.0.2 -> 3.0.3

On Tue, 7 Dec 2021 at 16:57, Khem Raj wrote: > > do_install_ptest () { > > +set -x > > I guess this is a remnant of debugging. Perhaps not needed here > Thanks, I added a followup patch to my queue. Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group.

Re: [OE-core] [PATCH 7/7] kern-tools: bug fixes and kgit-gconfig

On Tue, Dec 7, 2021 at 8:52 AM Bruce Ashfield wrote: > > From: Bruce Ashfield > > Bumping yocto-kernel-tools to version v0.3, which comprises the following > commits: > > 90598a5 tools: Makefile: add missing install file > 330f9fa kgit-config: fix file mode > 22b55cd kgit-config:

Re: [OE-core] [PATCH v3] tune-cortexa72: remove crypto for the default cortex-a72

On Tue, Dec 7, 2021 at 9:00 AM Jon Mason wrote: > > From: Jagadeesh Krishnanjanappa > > The cryptographic unit is optional for the Cortex-A72, but it was > included by default previously. This breaks building systems that > lack this functionality when using tune-cortexa72.inc. > > To correct

[OE-core] [PATCH v3] tune-cortexa72: remove crypto for the default cortex-a72

From: Jagadeesh Krishnanjanappa The cryptographic unit is optional for the Cortex-A72, but it was included by default previously. This breaks building systems that lack this functionality when using tune-cortexa72.inc. To correct this, add a crypto entry in the tune file. Since CRC is

[OE-core] [PATCH 6/7] linux-yocto-rt/5.10: update to -rt56

From: Bruce Ashfield Integrating the following commit(s) to linux-yocto-rt/5.10: 23f3ad608bc7 rcutorture: fixup merge from standard/base -stable 8612be3f3e2b Revert "rcutorture: Avoid problematic critical section nesting on RT" 9a6fb5667ac8 Linux 5.10.78-rt56 78c80dca8b1f irq_work: Also

[OE-core] [PATCH 3/7] linux-yocto/5.10: update to v5.10.82

From: Bruce Ashfield Updating linux-yocto/5.10 to the latest korg -stable release that comprises the following commits: d5259a9ba699 Linux 5.10.82 d35250ec5a23 Revert "perf: Rework perf_event_exit_event()" 6718f79c40fd ALSA: hda: hdac_stream: fix potential locking issue in

[OE-core] [PATCH 5/7] linux-yocto-dev: use versioned branch as default

From: Bruce Ashfield The -dev kernel used to only have standard/* branches, which were managed similarly to linux-next. Which means, they are for testing integration of patches, and are rebased as needed (typically on version changes). We now do some leading edge BSP development on the -dev

[OE-core] [PATCH 7/7] kern-tools: bug fixes and kgit-gconfig

From: Bruce Ashfield Bumping yocto-kernel-tools to version v0.3, which comprises the following commits: 90598a5 tools: Makefile: add missing install file 330f9fa kgit-config: fix file mode 22b55cd kgit-config: cleanup error message 1e2a233 kgit-config: fix the "not found"

Re: [OE-core] [PATCH] pango: upgrade 1.48.10 -> 1.50.0

And https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/2624/steps/12/logs/stdio, so that's x86-64 and arm64. Ross On Tue, 7 Dec 2021 at 16:51, Ross Burton wrote: > > Not just x32: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/2898/steps/12/logs/stdio > >

[OE-core] [PATCH 4/7] linux-yocto/5.15: update to v5.15.6

From: Bruce Ashfield Updating linux-yocto/5.15 to the latest korg -stable release that comprises the following commits: a2547651bc89 Linux 5.15.6 4268e8325d63 drm/amdgpu/gfx9: switch to golden tsc registers for renoir+ 8c501d9cf122 drm/amdgpu/gfx10: add wraparound gpu counter check for APUs as

[OE-core] [PATCH 1/7] linux-yocto/5.15: update to v5.15.5

From: Bruce Ashfield Updating linux-yocto/5.15 to the latest korg -stable release that comprises the following commits: f00712e27083 Linux 5.15.5 e6818963e0b0 ALSA: hda: hdac_stream: fix potential locking issue in snd_hdac_stream_assign() 01085644673f ALSA: hda: hdac_ext_stream: fix potential

[OE-core] [PATCH 2/7] linux-yocto/5.14: update to v5.14.21

From: Bruce Ashfield Updating linux-yocto/5.14 to the latest korg -stable release that comprises the following commits: 545728d9e085 Linux 5.14.21 999805aaf925 Revert "ACPI: scan: Release PM resources blocked by unused objects" 0750f769b958 thermal: Fix NULL pointer dereferences in of_thermal_

[OE-core] [PATCH 0/7] kernel: consolidated pull request

From: Bruce Ashfield Richard, Here's the next set of -stable updates, a -dev kernel branching tweak (as discussed on the mailing list) and the kernel tools that I presented during the YP summit. I also have patches to make 5.15 the default kernel for qemu*, but I wasn't sure if you wanted

Re: [OE-core] [PATCH] pango: upgrade 1.48.10 -> 1.50.0

Not just x32: https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/2898/steps/12/logs/stdio Ross On Tue, 7 Dec 2021 at 13:36, Richard Purdie wrote: > > On Mon, 2021-12-06 at 23:21 +0800, wangmy wrote: > > Signed-off-by: Wang Mingyu > > --- > > .../pango/{pango_1.48.10.bb =>

Re: [OE-core] [yocto] Help with Inclusive Language in OpenEmbedded/Yocto Project

Hi Jon, On 12/7/21 2:01 AM, Jon Mason wrote: > This email is a follow-up from the session held on Friday at the > OpenEmbedded Developer's Virtual Meeting (see > https://www.openembedded.org/wiki/OEDVM_Nov_2021) > > The session was not recorded, but the slides can be found at >

[OE-core] [PATCH] openssl: Use linux-latomic target for ARC

Some atomic ops for 32-bit ARC processors are implemented in GCC's libatomic. For example those dealing with 64-bit data (e.g. __atomic_load_8()) as well as some others. That said it's required to add "-latomic" for successful linkage. Otherwise error messages like this happen on OpenSSL building

Re: [OE-core] [PATCH 05/16] rustfmt: remove the recipe

On Tue, Dec 7, 2021 at 5:07 AM Alexander Kanavin wrote: > > There has been a discussion on the merits of keeping rustfmt in core, > and especially this message made me resubmit its removal: > > https://lists.openembedded.org/g/openembedded-core/message/157471 > Its fine I guess, perhaps

Re: [OE-core] [PATCH 15/16] ruby: update 3.0.2 -> 3.0.3

On Tue, Dec 7, 2021 at 5:07 AM Alexander Kanavin wrote: > > Do not tweak a file that is no longer installed. > > Signed-off-by: Alexander Kanavin > --- > meta/recipes-devtools/ruby/{ruby_3.0.2.bb => ruby_3.0.3.bb} | 5 ++--- > 1 file changed, 2 insertions(+), 3 deletions(-) > rename

Re: [OE-core] [PATCH 1/4] recipetool: Set master branch only as fallback

On Mon, 2021-12-06 at 09:04 +0100, Stefan Herbrechtsmeier wrote: > From: Stefan Herbrechtsmeier > > The commit 'meta/scripts: Manual git url branch additions (dc53fe75cc)' > sets the branch= parameter too early to master and thereby breaks the > -B/--srcbranch option. > > ERROR: branch=

[OE-core] Yocto Project Status WW49`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) *

[OE-core] [PATCH 2/2] documentation: Document PACKAGE_SNAP_LIB_SYMLINKS

PACKAGE_SNAP_LIB_SYMLINKS was added[1] originally to OpenEmbedded in 2008 and then to oe-core in 2011[2] but appears to have evaded documentation throughout that time. Let's add something that at least gives some clue as to what it does. Signed-off-by: Mike Crowe Signed-off-by: Phil Blundell

[OE-core] [PATCH 1/2] package: Only snap libraries if they would be processed by ldconfig OS-12840

PACKAGE_SNAP_LIB_SYMLINKS renames libraries based on their SONAME so that they can be found directly rather than going via symlinks that would be created by ldconfig. For example, without PACKAGE_SNAP_LIB_SYMLINKS in ${libdir} we have: libharfbuzz.so.0 -> libharfbuzz.so.0.20600.4

Re: [OE-core] [PATCH] libsdl2: upgrade 2.0.16 -> 2.0.18

On Tue, 2021-12-07 at 08:05 +0800, zhengruoqin wrote: > Remove unsupported option "--enable-sdl-dlopen". > > Changelog: > === > > General: > > The SDL wiki documentation and development headers are automatically kept in > sync > Each function has information about in which

Re: [OE-core] [PATCH] pango: upgrade 1.48.10 -> 1.50.0

On Mon, 2021-12-06 at 23:21 +0800, wangmy wrote: > Signed-off-by: Wang Mingyu > --- > .../pango/{pango_1.48.10.bb => pango_1.50.0.bb} | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > rename meta/recipes-graphics/pango/{pango_1.48.10.bb => pango_1.50.0.bb} > (94%) > >

[OE-core] [PATCH] systemd: Fix journal-gatewayd package name in USERADD_PACKAGES

The systemd-journal-gateway user and group are never added to an image since the package name added to USERADD_PACKES is wrong. Signed-off-by: Florian Amstutz --- meta/recipes-core/systemd/systemd_249.7.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[OE-core] [PATCH 16/16] libunwind: update 1.6.0 -> 1.6.2

Signed-off-by: Alexander Kanavin --- .../libunwind/libunwind/musl-header-conflict.patch| 4 ++-- .../libunwind/{libunwind_1.6.0.bb => libunwind_1.6.2.bb} | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) rename meta/recipes-support/libunwind/{libunwind_1.6.0.bb =>

[OE-core] [PATCH 11/16] libseccomp: update 2.5.2 -> 2.5.3

Drop all patches from MR https://github.com/seccomp/libseccomp/pull/327 as it has stalled, and rebasing them is non-trivial. Please land the changes upstream first. Drop 0001-configure.ac-Bump-version-to-2.5.99.patch as upstream has addressed the issue. Signed-off-by: Alexander Kanavin ---

[OE-core] [PATCH 13/16] git: upgrade 2.34.0 -> 2.34.1

The issue with COMPUTE_HEADER_DEPENDENCIES has been reported upstream, as it causes build races: https://lore.kernel.org/git/20211207113101.69686-1-alex.kana...@gmail.com/T/#u Signed-off-by: Alexander Kanavin --- meta/recipes-devtools/git/git.inc | 1 +

[OE-core] [PATCH 12/16] erofs-utils: update 1.3 -> 1.4

Signed-off-by: Alexander Kanavin --- ...0001-fsck-main.c-add-missing-include.patch | 26 +++ ...{erofs-utils_1.3.bb => erofs-utils_1.4.bb} | 6 +++-- 2 files changed, 30 insertions(+), 2 deletions(-) create mode 100644

[OE-core] [PATCH 15/16] ruby: update 3.0.2 -> 3.0.3

Do not tweak a file that is no longer installed. Signed-off-by: Alexander Kanavin --- meta/recipes-devtools/ruby/{ruby_3.0.2.bb => ruby_3.0.3.bb} | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) rename meta/recipes-devtools/ruby/{ruby_3.0.2.bb => ruby_3.0.3.bb} (93%) diff --git

[OE-core] [PATCH 14/16] go: update 1.17.3 -> 1.17.4

Signed-off-by: Alexander Kanavin --- meta/recipes-devtools/go/{go-1.17.3.inc => go-1.17.4.inc} | 2 +- ...{go-binary-native_1.17.3.bb => go-binary-native_1.17.4.bb} | 4 ++-- ...o-cross-canadian_1.17.3.bb => go-cross-canadian_1.17.4.bb} | 0 .../go/{go-cross_1.17.3.bb => go-cross_1.17.4.bb}

[OE-core] [PATCH 09/16] strace: update 5.14 -> 5.15

Signed-off-by: Alexander Kanavin --- ...1-Avoid-relying-on-presence-of-ipx.h.patch | 151 -- .../strace/{strace_5.14.bb => strace_5.15.bb} | 3 +- 2 files changed, 1 insertion(+), 153 deletions(-) delete mode 100644

[OE-core] [PATCH 08/16] rust: update 1.56.1 -> 1.57.0

Signed-off-by: Alexander Kanavin --- meta/conf/distro/include/tcmode-default.inc | 2 +- ...n_1.56.1.bb => cargo-cross-canadian_1.57.0.bb} | 0 .../cargo/{cargo_1.56.1.bb => cargo_1.57.0.bb}| 0 ...te-checksums-for-modified-files-for-rust.patch | 15 ++-

[OE-core] [PATCH 10/16] cups: update 2.3.3op2 -> 2.4.0

Mark no-hardcode-lib patch as upstreamable. Signed-off-by: Alexander Kanavin --- meta/recipes-extended/cups/cups.inc | 7 +-- .../cups/cups/libexecdir.patch| 50 +++ .../cups/{cups_2.3.3op2.bb => cups_2.4.0.bb} | 2 +- 3 files changed, 34

[OE-core] [PATCH 07/16] repo: update 2.17.3 -> 2.18

Replace a patch with a sed search-replace: this allows automated version updates, as the patch hardcoded the repo source revision. Signed-off-by: Alexander Kanavin --- .../0001-Set-REPO_REV-to-v2.17.3.patch| 35 --- .../repo/{repo_2.17.3.bb => repo_2.18.bb} | 9

[OE-core] [PATCH 06/16] python3-pycryptodome: update to 3.12.0

License-Update: dropped a patents clarification Signed-off-by: Alexander Kanavin --- meta/recipes-devtools/python/python-pycryptodome.inc | 4 +++- meta/recipes-devtools/python/python3-pycryptodome_3.11.0.bb | 5 - meta/recipes-devtools/python/python3-pycryptodome_3.12.0.bb | 5

[OE-core] [PATCH 05/16] rustfmt: remove the recipe

There has been a discussion on the merits of keeping rustfmt in core, and especially this message made me resubmit its removal: https://lists.openembedded.org/g/openembedded-core/message/157471 Signed-off-by: Alexander Kanavin --- meta/conf/distro/include/maintainers.inc | 1 -

[OE-core] [PATCH 04/16] serf: mark patches as inappropriate for upstream submission

Signed-off-by: Alexander Kanavin --- .../0001-buckets-ssl_buckets.c-do-not-use-ERR_GET_FUNC.patch | 3 ++- ...p.creating.directories.without.sandbox-install.prefix.patch | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git

[OE-core] [PATCH 03/16] libid3tag: move to meta-oe

There are no consumers in oe-core; years ago it used to be gstreamer. Signed-off-by: Alexander Kanavin --- meta/conf/distro/include/maintainers.inc | 1 - .../0001-Fix-gperf-3.1-incompatibility.patch | 40 - .../libid3tag/libid3tag/10_utf16.patch| 34

[OE-core] [PATCH 01/16] insane.bbclass: do not hardcode oe-core path in upstream-status check

Signed-off-by: Alexander Kanavin --- meta/classes/insane.bbclass | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass index 240f3aad62..8a47da5a09 100644 --- a/meta/classes/insane.bbclass +++

[OE-core] [PATCH 02/16] python3: drop unneeded multiprocessing module patch

I ran the reproducing sequence on qemux86, and it went fine: root@qemux86:~# python3 Python 3.10.0 (default, Oct 4 2021, 17:55:55) [GCC 11.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import multiprocessing >>> pool_sema =

Re: [OE-core] [dunfell][PATCH 00/14] Backport mandatory dtschema handling for device trees built through the kernel.

On 01/12/2021 21:33, Bruce Ashfield wrote: On Wed, Dec 1, 2021 at 3:34 PM Bhupesh Sharma wrote: This is a backport request for dunfell, while picking up only the skeletal support for allowing mandatory dtschema handling for device trees built through the kernel, introduced from kernel version

Re: [OE-core] [dunfell][PATCH 00/14] Backport mandatory dtschema handling for device trees built through the kernel.

On Tue, 2021-12-07 at 10:49 +0100, Nicolas Dechesne wrote: > > > On Wed, Dec 1, 2021 at 10:39 PM Richard Purdie > wrote: > > On Wed, 2021-12-01 at 16:33 -0500, Bruce Ashfield wrote: > > > On Wed, Dec 1, 2021 at 3:34 PM Bhupesh Sharma > > wrote: > > > > > > > > This is a backport request for

Re: [OE-core] [dunfell][PATCH 00/14] Backport mandatory dtschema handling for device trees built through the kernel.

On Wed, Dec 1, 2021 at 10:39 PM Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Wed, 2021-12-01 at 16:33 -0500, Bruce Ashfield wrote: > > On Wed, Dec 1, 2021 at 3:34 PM Bhupesh Sharma > wrote: > > > > > > This is a backport request for dunfell, while picking up only the > > >

[OE-core] [PATCH] qemuboot.bbclass: do_write_qemuboot_conf after wic

Allow to run do_write_qemuboot_conf later. The use case is to create a cryptographically signed firmware image with wic and boot it with runqemu. The signatures are generated by wic and forwarded to runqemu. Therefore do_write_qemuboot_conf must be allowed to run after do_image_wic.