From: Hongxu Jia <hongxu.jia@windriver.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"alex.kanavin@gmail.com" <alex.kanavin@gmail.com>
Subject: Re: [OE-core] [PATCH v2] vte: fix build failed for ppc64
Date: Mon, 9 Feb 2026 10:11:48 +0800 [thread overview]
Message-ID: <57514211-c8a8-4fa8-a9b2-5693930700d0@windriver.com> (raw)
In-Reply-To: <A1C75F2E-EB7E-431D-B4D0-9570DC3A4B19@arm.com>
On 2/6/26 23:07, Ross Burton 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 24 Dec 2025, at 03:16, hongxu via lists.openembedded.org <hongxu.jia=windriver.com@lists.openembedded.org> wrote:
>> +The source file subprojects/simdutf/simdutf.cpp is generated by python3
>> +script singleheader/amalgamate.py and the definition of write_v_u16_11bits_to_utf8
>> +and ppc64_convert_utf16_to_1_2_3_bytes_of_utf8 for ppc64 [1] requires option
>> +--with-utf16 and --with-latin1
>> +
>> +Add option --with-utf16 and --with-latin1 by default.
>> +
>> +[1] https://github.com/simdutf/simdutf/commit/497f4f29fe25a79af00ce25693a14682a5f669a5
>> +
>> +Upstream-Status: Submitted [https://gitlab.gnome.org/GNOME/vte/-/issues/2926]
> Upstream have closed this ticket, pointing at a fix in the simdutf repository instead. Is that possible to backport instead?
Please drop this patch, we do not maintain ppc64 any more
//Hongxu
>
> Ross
>
next prev parent reply other threads:[~2026-02-09 2:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 3:16 [PATCH v2] vte: fix build failed for ppc64 Hongxu Jia
2026-02-06 15:07 ` [OE-core] " Ross Burton
2026-02-09 2:11 ` Hongxu Jia [this message]
[not found] <1884086C67716646.1342979@lists.openembedded.org>
2025-12-24 4:49 ` Hongxu Jia
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=57514211-c8a8-4fa8-a9b2-5693930700d0@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=Ross.Burton@arm.com \
--cc=alex.kanavin@gmail.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