From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/libgtk4: bump to 4.18.2
Date: Mon, 21 Apr 2025 23:26:59 +0200 [thread overview]
Message-ID: <20250421232659.43f4ef55@windsurf> (raw)
In-Reply-To: <20250325101116.791637-2-thomas@devoogdt.com>
Hello Thomas,
On Tue, 25 Mar 2025 11:11:15 +0100
Thomas Devoogdt <thomas@devoogdt.com> wrote:
> https://gitlab.gnome.org/GNOME/gtk/-/blob/4.18.2/NEWS
>
> Note that libgtk4 never selected BR2_PACKAGE_CAIRO_{PNG,ZLIB} as it is
> not needed thanks to [1]. However, we need to select BR2_PACKAGE_LIBPNG [2].
> In libgtk3, this was indirectly done as libgtk3 selects BR2_PACKAGE_CAIRO_PNG.
>
> Also, add patches for:
> - toolchains without fenv.h. [3]
> - when cairo has been compiled without surfaces. [4]
>
> [1] https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/7717
> [2] https://gitlab.gnome.org/GNOME/gtk/-/blob/4.18.2/meson.build?ref_type=tags#L450
> [3] https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/7925
> [4] https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/7926
>
> Signed-off-by: Thomas Devoogdt <thomas@devoogdt.com>
Thanks for the new iteration!
> diff --git a/package/libgtk4/0002-gtk-gtkcssnumbervalue.c-fix-compilation-if-fenv.h-is.patch b/package/libgtk4/0002-gtk-gtkcssnumbervalue.c-fix-compilation-if-fenv.h-is.patch
> new file mode 100644
> index 0000000000..02d6a25526
> --- /dev/null
> +++ b/package/libgtk4/0002-gtk-gtkcssnumbervalue.c-fix-compilation-if-fenv.h-is.patch
> @@ -0,0 +1,106 @@
> +From e76e2c0c8afad80c6918890e443418e4f78c97c3 Mon Sep 17 00:00:00 2001
> +From: Thomas Devoogdt <thomas@devoogdt.com>
> +Date: Fri, 15 Nov 2024 08:22:40 +0100
> +Subject: [PATCH] gtk/gtkcssnumbervalue.c: fix compilation if fenv.h is missing
> +
> +../gtk/gtkcssnumbervalue.c:29:10: fatal error: fenv.h: No such file or directory
> + 29 | #include <fenv.h>
> + |
> +
> +Upstream: https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/7925
> +Signed-off-by: Thomas Devoogdt <thomas@devoogdt.com>
The feedback from upstream on this was pretty negative, and having to
maintain this forever doesn't seem like a great idea. There's already
quite a few packages that need fenv.h, and we for now address that with
ad-hoc architecture exclusions. Maybe it's time to bite the bullet, and
have some proper BR2_TOOLCHAIN_HAS_FENV_FE_DOWNWARD, etc so that we can
clean up all those dependencies?
You can "git grep fenv" in Buildroot to see the packages that have
fenv-related issues.
And yes, that means libgtk4 would not be available for certain
architecture/libc combinations, and I think that's fine.
Thanks!
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-04-21 21:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 16:08 [Buildroot] [PATCH v2] package/libgtk4: bump to 4.17.0 Thomas Devoogdt
2025-01-25 21:07 ` [Buildroot] [PATCH v2] package/libgtk4: bump to 4.17.3 Thomas Devoogdt
2025-02-05 15:37 ` Thomas Petazzoni via buildroot
2025-03-25 10:11 ` [Buildroot] [PATCH v2] package/wayland-protocols: bump to 1.42 Thomas Devoogdt
2025-03-25 10:11 ` [Buildroot] [PATCH v2] package/libgtk4: bump to 4.18.2 Thomas Devoogdt
2025-04-21 21:26 ` Thomas Petazzoni via buildroot [this message]
2025-03-25 21:50 ` [Buildroot] [PATCH v2] package/wayland-protocols: bump to 1.42 Julien Olivain
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=20250421232659.43f4ef55@windsurf \
--to=buildroot@buildroot.org \
--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.