From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org, Adrian Perez de Castro <aperez@igalia.com>
Subject: Re: [Buildroot] [PATCH] package/webkitgtk: propagate gst1-libav architecture dependency
Date: Sun, 13 Sep 2026 21:36:48 +0200 [thread overview]
Message-ID: <75ec7478887f4b7a618200bd58b57c66@free.fr> (raw)
In-Reply-To: <20260913170133.1695626-1-thomas.petazzoni@bootlin.com>
On 13/09/2026 19:01, Thomas Petazzoni via buildroot wrote:
> BR2_PACKAGE_WEBKITGTK_MULTIMEDIA selects BR2_PACKAGE_GST1_LIBAV, which
> depends on BR2_PACKAGE_FFMPEG_ARCH_SUPPORTS, but doesn't propagate
> this dependency. In practice, there is no issue, as webkitgtk is only
> available on a subset of CPU architectures, while
> BR2_PACKAGE_FFMPEG_ARCH_SUPPORTS makes ffmpeg available on pretty much
> all CPU architectures, except Cortex-M, m68k coldfire, and some
> specific cases of OpenRISC, which are not supported by webkitgtk.
>
> But for the sake of having correct dependency propagation, let's fix
> this.
>
> The other packages selected by BR2_PACKAGE_WEBKITGTK_MULTIMEDIA have
> dependencies that are already handled at the top-level
> BR2_PACKAGE_WEBKITGTK option.
>
> Fixes: e6e549b9e40d42dbb6a551ecaeb040c1e401f21a ("ffmpeg: add
> BR2_PACKAGE_FFMPEG_ARCH_SUPPORTS")
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-09-13 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 17:01 [Buildroot] [PATCH] package/webkitgtk: propagate gst1-libav architecture dependency Thomas Petazzoni via buildroot
2026-09-13 19:36 ` Julien Olivain via buildroot [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=75ec7478887f4b7a618200bd58b57c66@free.fr \
--to=buildroot@buildroot.org \
--cc=aperez@igalia.com \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.