From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: James Hilliard <james.hilliard1@gmail.com>,
Thomas Devoogdt <thomas.devoogdt@barco.com>,
buildroot@buildroot.org,
Adrian Perez de Castro <aperez@igalia.com>
Subject: Re: [Buildroot] [PATCH v3 2/2] package/webkitgtk: bump to 2.46.4
Date: Mon, 6 Jan 2025 16:39:49 +0100 [thread overview]
Message-ID: <20250106163949.5c49b568@windsurf> (raw)
In-Reply-To: <CACXRmJi=rGj9uA6R3fQ45sKuSy_+=Vi6u_Vdn_koVd4DkWZj8w@mail.gmail.com>
Hello Thomas,
Happy New Year and best wishes for 2025!
On Mon, 30 Dec 2024 18:31:31 +0100
Thomas Devoogdt <thomas@devoogdt.com> wrote:
> >> Do you have a defconfig that exhibits the issue?
>
> I just used the test-pkg tool to figure this out.
>
> $ cat webkitgtk.config
> BR2_PACKAGE_WAYLAND=y
> BR2_PACKAGE_MESA3D=y
> BR2_PACKAGE_MESA3D_OPENGL_EGL=y
> BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_SWRAST=y
> BR2_PACKAGE_LIBGTK3=y
> BR2_PACKAGE_WEBKITGTK=y
> BR2_PACKAGE_WEBKITGTK_MINIBROWSER=y
>
> $ ./utils/test-pkg -p webkitgtk -c webkitgtk.config
Thanks for providing this snippet.
> All builds will fail due to the same reason. Are there other possible
> side effects?; I don't know. All I know is that a similar issue was
> fixed years ago, which was re-introduced by bumping pkg-config. Btw, I
> was searching https://autobuild.buildroot.org/ for this issue, but I
> didn't find any webkitgtk build. Is there a reason why this one has
> never been compiled?
Webkitgtk is a huge beast with a lot of dependencies. Therefore, there
is a significant chance that something else fails in the build before
that...
You can find all builds that had BR2_PACKAGE_WEBKITGTK=y by using:
http://autobuild.buildroot.net/index.php?symbols%5BBR2_PACKAGE_WEBKITGTK%5D=y
but as you can see, all of them failed on some other package, most
likely even before getting to webkitgtk.
Ah and also: webkitgtk starts with a "w". So if nothing depends on
webkitgtk, webkitgtk is going to be the last package to be built.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-01-06 15:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-31 12:07 [Buildroot] [PATCH v1] package/webkitgtk: bump to 2.44.3 Thomas Devoogdt
2024-09-01 14:13 ` Adrian Perez de Castro
2024-09-05 20:47 ` Thomas Petazzoni via buildroot
2024-09-17 20:33 ` [Buildroot] [PATCH v2] package/webkitgtk: bump to 2.44.4 Thomas Devoogdt
2024-12-16 18:17 ` [Buildroot] [PATCH v3 1/2] " Thomas Devoogdt
2024-12-16 18:17 ` [Buildroot] [PATCH v3 2/2] package/webkitgtk: bump to 2.46.4 Thomas Devoogdt
2024-12-16 21:28 ` Thomas Devoogdt
2024-12-16 21:40 ` Thomas Devoogdt
2024-12-17 22:20 ` Thomas Devoogdt
2024-12-18 8:43 ` [Buildroot] [PATCH v1] package/pkgconf: fix sysroot being prepended twice to the pkgdatadir path Thomas Devoogdt
2025-02-04 12:41 ` Thomas Devoogdt
2025-02-26 14:38 ` Peter Korsgaard
2025-02-26 18:14 ` Thomas Devoogdt
2025-03-13 20:38 ` Peter Korsgaard
2024-12-29 22:02 ` [Buildroot] [PATCH v3 2/2] package/webkitgtk: bump to 2.46.4 Thomas Petazzoni via buildroot
2024-12-30 17:31 ` Thomas Devoogdt
2025-01-06 15:39 ` Thomas Petazzoni via buildroot [this message]
2025-03-02 19:56 ` Thomas Devoogdt
2025-03-12 19:01 ` Peter Korsgaard
2025-03-22 7:29 ` Peter Korsgaard
2025-02-04 15:20 ` [Buildroot] [PATCH v3 1/2] package/webkitgtk: bump to 2.44.4 Peter Korsgaard
2025-02-07 19:48 ` Peter Korsgaard
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=20250106163949.5c49b568@windsurf \
--to=buildroot@buildroot.org \
--cc=aperez@igalia.com \
--cc=james.hilliard1@gmail.com \
--cc=thomas.devoogdt@barco.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=thomas@devoogdt.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.