From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org, Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/cairo: Fix build with newer gcc
Date: Fri, 2 Jan 2026 23:39:04 +0100 [thread overview]
Message-ID: <20260102233904.426f2e8b@windsurf> (raw)
In-Reply-To: <20251125210759.333290-1-bernd@kuhls.net>
Hello Bernd,
On Tue, 25 Nov 2025 22:07:59 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:
> Fixes:
> https://autobuild.buildroot.net/results/0e9/0e962c66e1e96b5899e87c13ace824379adc09f9/
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
In the spirit of recent discussions, could you respin this patch with a
more specific description, by doing some actual testing: what was the
last GCC version that built cairo successfully, and with which GCC
version did it start failing.
> ---
> .../0001-Wincompatible-pointer-types.patch | 38 +++++++++++++++++++
> 1 file changed, 38 insertions(+)
> create mode 100644 package/cairo/0001-Wincompatible-pointer-types.patch
>
> diff --git a/package/cairo/0001-Wincompatible-pointer-types.patch b/package/cairo/0001-Wincompatible-pointer-types.patch
> new file mode 100644
> index 0000000000..79f0347538
> --- /dev/null
> +++ b/package/cairo/0001-Wincompatible-pointer-types.patch
> @@ -0,0 +1,38 @@
> +Fix build with newer gcc
> +
> +Downloaded from
> +https://github.com/LibreOffice/core/blob/master/external/cairo/cairo/Wincompatible-pointer-types.patch.0
This link doesn't work anymore, because you pointed to the master
branch, from which this patch has probably been removed.
> +
> +Upstream: https://gitlab.freedesktop.org/cairo/cairo/-/issues/921
> +
> +Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Cairo is using Git as its version control-system, so this patch should
be Git-formatted.
I see this hasn't been fixed upstream, while Cairo is widely used and
well-maintained. Why only us are hitting the issue? Not Fedora, Arch,
etc. who use bleeding-edge GCC compilers? Presumably the upstream Cairo
developers are also using an up-to-date distro, so why didn't they fix
the issue?
Is the issue perhaps happening only with a certain C library? Or maybe
it isn't gcc version related after all, or?
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
prev parent reply other threads:[~2026-01-02 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 21:07 [Buildroot] [PATCH 1/1] package/cairo: Fix build with newer gcc Bernd Kuhls
2026-01-02 22:39 ` Thomas Petazzoni 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=20260102233904.426f2e8b@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=fontaine.fabrice@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox