From: Hongxu Jia <hongxu.jia@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org, alex@linutronix.de,
mathieu.dubois-briand@bootlin.com
Subject: Re: [OE-core] [PATCH 2/2] webkitgtk: upgrade 2.50.0 -> 2.50.4
Date: Mon, 19 Jan 2026 10:26:42 +0800 [thread overview]
Message-ID: <c586a89f-3e84-4e74-8e03-6598045fd501@windriver.com> (raw)
In-Reply-To: <188A774745AD7FE0.3093368@lists.openembedded.org>
Ping,
On 1/14/26 10:15, hongxu via lists.openembedded.org wrote:
> On 1/13/26 23:25, Alexander Kanavin wrote:
>> CAUTION: This email comes from a non Wind River email account!
>> Do not click links or open attachments unless you recognize the
>> sender and know the content is safe.
>>
>> On Tue, 13 Jan 2026 at 13:45, hongxu via lists.openembedded.org
>> <hongxu.jia=windriver.com@lists.openembedded.org> wrote:
>>> Drop backport fix-musl-compilation.patch which already exists
>>> in 2.50.4
>>>
>>> Signed-off-by: Alexander Kanavin <alex@linutronix.de>
>>>
>>> - Fix compile failure on qemux86 [1] to
>>> drop fix_op_instanceof_handler_for_32-bit_C-loop_build.patch,
>>> which conflicts with upstream solution [2]
>>>
>>> - Fix compile failure on qemuriscv64
>>> ...
>>> Source/ThirdParty/skia/modules/skcms/src/Transform_inl.h:810:71:
>>> error: cannot tail-call: tail call production failed
>>> 810 | DECLARE_STAGE(name, arg, [[clang::musttail]] return
>>> (*list.fn)(list, ctx, src, dst, \
>>> | ~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~
>>> 811 | r, g, b, a, i))
>>> | ~~~~~~~~~~~~~~
>>> ...
>>>
>>> [1]
>>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/2907
>>> [2]
>>> https://github.com/WebKit/WebKit/commit/fcaa289f6015595a638eb96b9f728eaaa7b13ab8
>>>
>>> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
>>> +# Fix Source/ThirdParty/skia/modules/skcms/src/Transform_inl.h:810:71:
>>> +# error: cannot tail-call: tail call production failed
>>> +CXXFLAGS:append:riscv64 = " -DSKCMS_HAS_MUSTTAIL=0"
>> Thanks for completing the update. Perhaps this last risc-v tweak
>> should be reported with an upstream ticket?
>
> Sure, I will try it later
>
File https://bugs.webkit.org/show_bug.cgi?id=305745 for upstream
//Hongxu
> //Hongxu
>
>> Alex
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#229301): https://lists.openembedded.org/g/openembedded-core/message/229301
> Mute This Topic: https://lists.openembedded.org/mt/117242049/3617049
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [hongxu.jia@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2026-01-19 2:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 12:45 [PATCH 1/2] flac: fix compile failed on musl Hongxu Jia
2026-01-13 12:45 ` [PATCH 2/2] webkitgtk: upgrade 2.50.0 -> 2.50.4 Hongxu Jia
2026-01-13 15:25 ` [OE-core] " Alexander Kanavin
2026-01-14 2:15 ` Hongxu Jia
[not found] ` <188A774745AD7FE0.3093368@lists.openembedded.org>
2026-01-19 2:26 ` Hongxu Jia [this message]
2026-01-19 12:45 ` Alexander Kanavin
2026-01-19 18:07 ` [OE-core] [PATCH 1/2] flac: fix compile failed on musl Ross Burton
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=c586a89f-3e84-4e74-8e03-6598045fd501@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
/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