From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org, Carsten Schoenert <c.schoenert@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/libsvg: fix build with gcc 14.x
Date: Sat, 27 Dec 2025 16:44:45 +0100 [thread overview]
Message-ID: <20251227164445.37daa273@windsurf> (raw)
In-Reply-To: <20251027191829.1129021-1-bernd@kuhls.net>
Hello Bernd,
On Mon, 27 Oct 2025 20:18:29 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:
> Fixes:
> https://autobuild.buildroot.net/results/12e/12e2481afb8acd3149f7ce5692d0f113f2419cd3/
>
> No active upstream was found:
> https://lists.freedesktop.org/pipermail/cairo/2010-July/020272.html
> https://www.freshports.org/graphics/libsvg/
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> package/libsvg/0003-stdlib.patch | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
> create mode 100644 package/libsvg/0003-stdlib.patch
Thanks for the patch. However:
- The problem also occurs with GCC 13.x, so it's not a GCC 14.x issue
- On my side, I also have build failures like this:
svgint.h:40:9: error: unknown type name 'xmlParserCtxtPtr'
40 | typedef xmlParserCtxtPtr svg_xml_parser_context_t;
| ^~~~~~~~~~~~~~~~
as visible at https://autobuild.buildroot.net/results/895/895fdba2f3fcaa42aa93946f2532351d39b16647/build-end.log
So since the latest release of libsvg-cairo and libsvg was from 2005, I
sent a patch series to just drop both packages:
https://lore.kernel.org/buildroot/20251227154005.2015199-1-thomas.petazzoni@bootlin.com/
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-12-27 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 19:18 [Buildroot] [PATCH 1/1] package/libsvg: fix build with gcc 14.x Bernd Kuhls
2025-12-27 15:44 ` 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=20251227164445.37daa273@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=c.schoenert@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