From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
Cc: "Giulio Benetti" <giulio.benetti@benettiengineering.com>,
"Alexis Lothoré" <alexis.lothore@bootlin.com>,
"Julien Corjon" <corjon.j@ecagroup.com>
Subject: Re: [Buildroot] [PATCH 2/2] package/qt5/qt5webkit: fix WebCore compatibility issue with updated libxml2
Date: Fri, 12 Jul 2024 15:45:15 +0200 [thread overview]
Message-ID: <20240712154515.43ac3d55@windsurf> (raw)
In-Reply-To: <20240313224610.2743219-3-alexis.lothore@bootlin.com>
On Wed, 13 Mar 2024 23:46:10 +0100
Alexis Lothoré via buildroot <buildroot@buildroot.org> wrote:
> From: Alexis Lothoré <alexis.lothore@bootlin.com>
>
> qt5webkit build currently breaks on the following error:
>
> XSLStyleSheetLibxslt.cpp:148:129: error: invalid conversion from ‘void (*)(void*, xmlError*)’ {aka ‘void (*)(void*, _xmlError*)’} to ‘xmlStructuredErrorFunc’ {aka ‘void (*)(void*, const _xmlError*)’} [-fpermissive]
> 148 | XMLDocumentParserScope scope(cachedResourceLoader(), XSLTProcessor::genericErrorFunc, XSLTProcessor::parseErrorFunc, console);
> | ^
> | |
> | void (*)(void*, xmlError*) {aka void (*)(void*, _xmlError*)}
>
> This error is due to an API update in libxml2, enforcing const on more
> struct in version 2.12.0 (see [1]). Buildroot now tracks v2.12.5.
> Upstream Webkit project has already issued the corresponding fix ([2]),
> which updates corresponding internal prototypes depending on libxml2
> version, but the qt5webkit version tracked in buildroot does not integrate
> the corresponding Webkit version.
>
> Fix this build issue by bringing the upstream patch "as is" from Webkit
>
> [1] https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.12.0
> [2] https://github.com/WebKit/WebKit/commit/1bad176b2496579d760852c80cff3ad9fb7c3a4b
>
> Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
> ---
> ...-libxml2-version-2.12.0-due-to-API-c.patch | 61 +++++++++++++++++++
> 1 file changed, 61 insertions(+)
> create mode 100644 package/qt5/qt5webkit/0008-Build-fails-with-libxml2-version-2.12.0-due-to-API-c.patch
Applied to master, thanks. I couldn't add any autobuilder reference,
because this issue was apparently "hidden" behind the issue fixed in
PATCH 1/2. 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
next prev parent reply other threads:[~2024-07-12 13:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 22:46 [Buildroot] [PATCH 0/2] package/qt5/qt5webkit: backport upstream patches to fix build Alexis Lothoré via buildroot
2024-03-13 22:46 ` [Buildroot] [PATCH 1/2] package/qt5/qt5webkit: fix JavaScriptCore parser error Alexis Lothoré via buildroot
2024-07-12 13:45 ` Thomas Petazzoni via buildroot
2024-07-31 16:35 ` Peter Korsgaard
2024-03-13 22:46 ` [Buildroot] [PATCH 2/2] package/qt5/qt5webkit: fix WebCore compatibility issue with updated libxml2 Alexis Lothoré via buildroot
2024-07-12 13:45 ` Thomas Petazzoni via buildroot [this message]
2024-07-31 16:35 ` 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=20240712154515.43ac3d55@windsurf \
--to=buildroot@buildroot.org \
--cc=alexis.lothore@bootlin.com \
--cc=corjon.j@ecagroup.com \
--cc=giulio.benetti@benettiengineering.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