From: Hongxu Jia <hongxu.jia@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] vte: fix build failed for ppc64
Date: Wed, 24 Dec 2025 11:14:53 +0800 [thread overview]
Message-ID: <aa268342-7075-41e7-a60b-470de870b6b8@windriver.com> (raw)
In-Reply-To: <CANNYZj-rHr0YQewsyj30cUHNtm2vLJ7iwb4NonudHYxnUg2gqA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1903 bytes --]
On 12/23/25 18:27, 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, 23 Dec 2025 at 09:55, hongxu via lists.openembedded.org
> <hongxu.jia=windriver.com@lists.openembedded.org> wrote:
>> +Upstream-Status: Inappropriate [Yocto specific for ppc64]
>> +
>> +Signed-off-by: Hongxu Jia<hongxu.jia@windriver.com>
>> +---
>> + meson.build | 3 ++-
>> + 1 file changed, 2 insertions(+), 1 deletion(-)
>> +
>> +diff --git a/meson.build b/meson.build
>> +index 330ee89..a6c64ca 100644
>> +--- a/meson.build
>> ++++ b/meson.build
>> +@@ -41,10 +41,11 @@ simdutf_amalgamate = [
>> + '--no-zip',
>> + '--no-readme',
>> + '--with-utf8',
>> +- # '--with-utf16',
>> ++ '--with-utf16',
>> + '--with-utf32',
>> + # '--with-base64',
>> + # '--with-detect-enc',
>> ++ '--with-latin1',
>> + '--with-ascii',
> Why these particular options are necessary on powerpc64 but not other
> targets? They do not seem specific to that platform.
The upstream simdutf newly supports for ppc64 [1], and define
function write_v_u16_11bits_to_utf8 and
ppc64_convert_utf16_to_1_2_3_bytes_of_utf8 for ppc64,
and apply them with option --with-utf16 and --with-latin1
[1]
https://github.com/simdutf/simdutf/commit/497f4f29fe25a79af00ce25693a14682a5f669a5
> Also carrying conditional patches for configurations that aren't
> tested in CI is prone to quiet regressions (including such patches
> failing to apply after a version update). I'd say you need to both
> investigate a bit deeper, and raise the issue with both vte and
> simdutf upstreams.
File an issue for upstream vte
https://gitlab.gnome.org/GNOME/vte/-/issues/2926
Submitted a patch to add option --with-utf16 and --with-latin1 by default,
attached the patch along with the issue
//Hongxu
> Alex
[-- Attachment #2: Type: text/html, Size: 3387 bytes --]
prev parent reply other threads:[~2025-12-24 3:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 8:54 [PATCH] vte: fix build failed for ppc64 Hongxu Jia
2025-12-23 10:27 ` [OE-core] " Alexander Kanavin
2025-12-24 3:14 ` Hongxu Jia [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=aa268342-7075-41e7-a60b-470de870b6b8@windriver.com \
--to=hongxu.jia@windriver.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