public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: openembedded-core@lists.openembedded.org, alex.kanavin@gmail.com
Subject: Re: [OE-core] [PATCH v2] vte: fix build failed for ppc64
Date: Wed, 24 Dec 2025 12:49:37 +0800	[thread overview]
Message-ID: <45f2d106-ad3e-4746-88c7-4df90b274bda@windriver.com> (raw)
In-Reply-To: <1884086C67716646.1342979@lists.openembedded.org>

Please drop this v2,
there is slightly differ between development git vs released tarball for 
vte,
I need to tweak the patch for release tarball, v3 incoming

//Hongxu

On 12/24/25 11:16, hongxu via lists.openembedded.org wrote:
> $ echo 'MACHINE = "qemuppc64"' >> conf/local.conf
> $ bitbake vte
> ...
> |subprojects/simdutf/simdutf.cpp:20533:7: error: there are no arguments to 'write_v_u16_11bits_to_utf8' that depend on a template parameter, so a declaration of 'write_v_u16_11bits_to_utf8' must be available [-Wtemplate-body]
> |20533 |       write_v_u16_11bits_to_utf8(
> |      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~
> |subprojects/simdutf/simdutf.cpp:20533:7: note: (if you use '-fpermissive', G++ will accept your code, but allowing the use of an undeclared name is deprecated)
> |subprojects/simdutf/simdutf.cpp:20559:7: error: there are no arguments to 'ppc64_convert_utf16_to_1_2_3_bytes_of_utf8' that depend on a template parameter, so a declaration of 'ppc64_convert_utf16_to_1_2_3_bytes_of_utf8' must be available [-Wtemplate-body]
> |20559 |       ppc64_convert_utf16_to_1_2_3_bytes_of_utf8(
> |      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> |subprojects/simdutf/simdutf.cpp:20533:33: error: 'write_v_u16_11bits_to_utf8' was not declared in this scope
> |20533 |       write_v_u16_11bits_to_utf8(
> |      |       ~~~~~~~~~~~~~~~~~~~~~~~~~~^
> |20534 |           in, utf8_output, as_vector_u8(one_byte_bytemask), one_byte_bitmask);
> |      |           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ...
>
> 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
>
> [1] https://github.com/simdutf/simdutf/commit/497f4f29fe25a79af00ce25693a14682a5f669a5
>
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
>   ...-fix-compile-simdutf-failed-on-ppc64.patch | 57 +++++++++++++++++++
>   meta/recipes-support/vte/vte_0.82.1.bb        |  1 +
>   2 files changed, 58 insertions(+)
>   create mode 100644 meta/recipes-support/vte/vte/0001-build-fix-compile-simdutf-failed-on-ppc64.patch
>
> diff --git a/meta/recipes-support/vte/vte/0001-build-fix-compile-simdutf-failed-on-ppc64.patch b/meta/recipes-support/vte/vte/0001-build-fix-compile-simdutf-failed-on-ppc64.patch
> new file mode 100644
> index 0000000000..d84630c164
> --- /dev/null
> +++ b/meta/recipes-support/vte/vte/0001-build-fix-compile-simdutf-failed-on-ppc64.patch
> @@ -0,0 +1,57 @@
> +From 26e55adb9bd03fbd50bdce63aef8effc2d02b634 Mon Sep 17 00:00:00 2001
> +From: Hongxu Jia <hongxu.jia@windriver.com>
> +Date: Tue, 23 Dec 2025 18:28:29 -0800
> +Subject: [PATCH] build: fix compile simdutf failed on ppc64
> +
> +...
> +|subprojects/simdutf/simdutf.cpp:20533:7: error: there are no arguments to 'write_v_u16_11bits_to_utf8' that depend on a template parameter, so a declaration of 'write_v_u16_11bits_to_utf8' must be available [-Wtemplate-body]
> +|20533 |       write_v_u16_11bits_to_utf8(
> +|      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~
> +|subprojects/simdutf/simdutf.cpp:20533:7: note: (if you use '-fpermissive', G++ will accept your code, but allowing the use of an undeclared name is deprecated)
> +|subprojects/simdutf/simdutf.cpp:20559:7: error: there are no arguments to 'ppc64_convert_utf16_to_1_2_3_bytes_of_utf8' that depend on a template parameter, so a declaration of 'ppc64_convert_utf16_to_1_2_3_bytes_of_utf8' must be available [-Wtemplate-body]
> +|20559 |       ppc64_convert_utf16_to_1_2_3_bytes_of_utf8(
> +|      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +|subprojects/simdutf/simdutf.cpp:20533:33: error: 'write_v_u16_11bits_to_utf8' was not declared in this scope
> +|20533 |       write_v_u16_11bits_to_utf8(
> +|      |       ~~~~~~~~~~~~~~~~~~~~~~~~~~^
> +|20534 |           in, utf8_output, as_vector_u8(one_byte_bytemask), one_byte_bitmask);
> +|      |           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +...
> +
> +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]
> +
> +Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> +---
> + subprojects/packagefiles/simdutf/meson.build | 3 ++-
> + 1 file changed, 2 insertions(+), 1 deletion(-)
> +
> +diff --git a/subprojects/packagefiles/simdutf/meson.build b/subprojects/packagefiles/simdutf/meson.build
> +index 330ee89f..ab934c30 100644
> +--- a/subprojects/packagefiles/simdutf/meson.build
> ++++ b/subprojects/packagefiles/simdutf/meson.build
> +@@ -41,11 +41,12 @@ simdutf_amalgamate = [
> +   '--no-zip',
> +   '--no-readme',
> +   '--with-utf8',
> +-  # '--with-utf16',
> ++  '--with-utf16',
> +   '--with-utf32',
> +   # '--with-base64',
> +   # '--with-detect-enc',
> +   '--with-ascii',
> ++  '--with-latin1',
> + ]
> +
> + if get_option('debug')
> +--
> +2.49.0
> +
> diff --git a/meta/recipes-support/vte/vte_0.82.1.bb b/meta/recipes-support/vte/vte_0.82.1.bb
> index b5d6f2fb62..0a2535f21e 100644
> --- a/meta/recipes-support/vte/vte_0.82.1.bb
> +++ b/meta/recipes-support/vte/vte_0.82.1.bb
> @@ -19,6 +19,7 @@ inherit gnomebase gi-docgen features_check upstream-version-is-even gobject-intr
>   
>   SRC_URI += "file://0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch \
>               file://0001-support-reproducibility-for-debug-sources.patch;patchdir=./subprojects/simdutf \
> +            file://0001-build-fix-compile-simdutf-failed-on-ppc64.patch \
>   "
>   
>   SRC_URI[archive.sha256sum] = "79376d70402d271e2d38424418e1aea72357934d272e321e3906b71706a78e3a"
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#228514): https://lists.openembedded.org/g/openembedded-core/message/228514
> Mute This Topic: https://lists.openembedded.org/mt/116925096/3617049
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [hongxu.jia@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>



       reply	other threads:[~2025-12-24  4:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1884086C67716646.1342979@lists.openembedded.org>
2025-12-24  4:49 ` Hongxu Jia [this message]
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

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=45f2d106-ad3e-4746-88c7-4df90b274bda@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