From: Denys Dmytriyenko <denis@denix.org>
To: a-christidis@ti.com
Cc: Ryan Eatmon <reatmon@ti.com>,
t-lannynd@ti.com, meta-arago@lists.yoctoproject.org,
detheridge@ti.com, b-brnich@ti.com
Subject: Re: [meta-arago][master][PATCH] chromium: Add a patch to fix build against GLIBC 2.43
Date: Tue, 17 Mar 2026 16:18:15 -0400 [thread overview]
Message-ID: <20260317201815.GD11121@denix.org> (raw)
In-Reply-To: <d3cb5d89-1668-4d7b-bb4a-b662152a7fb8@ti.com>
On Tue, Mar 17, 2026 at 03:01:22PM -0500, Antonios Christidis via lists.yoctoproject.org wrote:
>
> On 3/17/26 2:56 PM, Ryan Eatmon wrote:
> >
> >
> >On 3/17/2026 2:38 PM, Thorsten Lannynd via lists.yoctoproject.org wrote:
> >>An update to oe-core leads to build failures with Chromium v142.
> >>This fix
> >>is currently pending in meta-browser but is needed to get
> >>Chromium to build
> >>succesfully.
> >>
> >>https://github.com/OSSystems/meta-browser/pull/962/changes/4e450497be557fc4b5ff1397f78fa0f8381e281d
> >>
> >>
> >>Signed-off-by: Thorsten Lannynd <t-lannynd@ti.com>
> >>---
> >> .../fix-SYS_SECCOMP-redefinition.patch | 16 ++++++++++++++++
> >> .../chromium/chromium-ozone-wayland-arago.inc | 1 +
> >> 2 files changed, 17 insertions(+)
> >> create mode 100644 meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland-142.0.7444.175/fix-SYS_SECCOMP-redefinition.patch
> >>
> >>diff --git a/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland-142.0.7444.175/fix-SYS_SECCOMP-redefinition.patch b/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland-142.0.7444.175/fix-SYS_SECCOMP-redefinition.patch
> >>
> >>new file mode 100644
> >>index 00000000..594729b3
> >>--- /dev/null
> >>+++ b/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland-142.0.7444.175/fix-SYS_SECCOMP-redefinition.patch
> >>@@ -0,0 +1,16 @@
> >>+Taken from:
> >>+https://aur.archlinux.org/cgit/aur.git/tree/0007-qt5-webengine-glibc-2.43-SYS_SECCOMP-as-enum@chromium.patch?h=qt5-webengine
> >>
> >>+
> >>+Upstream-Status: Inappropriate [glibc 2.43 fix]
> >
> >I would argue that this is not "Inappropriate" as this is not an
> >OE specific kind of change. This should either be a Backport of a
> >patch that is pending on meta-browser, or Pending if you have
> >submitted this patch to the chromium project itself.
> >
> Could this be "Submitted [link]", link pointing to https://github.com/OSSystems/meta-browser/pull/962/changes/4e450497be557fc4b5ff1397f78fa0f8381e281d
> ?
Yes, this sounds correct ^^^
> >>+diff --git a/sandbox/linux/system_headers/linux_seccomp.h
> >>b/sandbox/linux/system_headers/linux_seccomp.h
> >>+index 8690a96eb0..8988836508 100644
> >>+--- a/sandbox/linux/system_headers/linux_seccomp.h
> >>++++ b/sandbox/linux/system_headers/linux_seccomp.h
> >>+@@ -6,6 +6,7 @@
> >>+ #define SANDBOX_LINUX_SYSTEM_HEADERS_LINUX_SECCOMP_H_
> >>+
> >>+ #include <stdint.h>
> >>++#include <signal.h>
> >>+ #include <sys/ioctl.h>
> >>+
> >>+ #include "build/build_config.h"
> >>diff --git a/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland-arago.inc b/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland-arago.inc
> >>
> >>index 5b0f2703..3ec0610a 100644
> >>--- a/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland-arago.inc
> >>+++ b/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland-arago.inc
> >>@@ -9,6 +9,7 @@ SRC_URI:append = " \
> >>file://0002-chromium-gpu-sandbox-Allow-GPU-sandbox-access-to-V4L.patch \
> >>file://0003-chromium-gpu-v4l2-Fix-OUTPUT-queue-streaming-in-V4L2.patch \
> >>file://0004-media-gpu-v4l2-Avoid-placing-incomplete-H264-access-.patch \
> >>+ file://fix-SYS_SECCOMP-redefinition.patch \
> >> "
> >> # Override do_copy_clang_library to handle both target and
> >>host architectures
prev parent reply other threads:[~2026-03-17 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 19:38 [meta-arago][master][PATCH] chromium: Add a patch to fix build against GLIBC 2.43 Thorsten Lannynd
2026-03-17 19:43 ` PRC Automation
2026-03-17 19:56 ` Ryan Eatmon
2026-03-17 20:01 ` Antonios Christidis
2026-03-17 20:18 ` Denys Dmytriyenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260317201815.GD11121@denix.org \
--to=denis@denix.org \
--cc=a-christidis@ti.com \
--cc=b-brnich@ti.com \
--cc=detheridge@ti.com \
--cc=meta-arago@lists.yoctoproject.org \
--cc=reatmon@ti.com \
--cc=t-lannynd@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox