From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <ankur.tyagi85@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH v2] vte: upgrade 0.82.2 -> 0.84.0
Date: Fri, 27 Mar 2026 09:41:50 +0100 [thread overview]
Message-ID: <DHDFIRLFWLM2.MENHJ5825HET@bootlin.com> (raw)
In-Reply-To: <20260326190427.2198044-1-ankur.tyagi85@gmail.com>
On Thu Mar 26, 2026 at 8:04 PM CET, Ankur Tyagi via lists.openembedded.org wrote:
> From: Ankur Tyagi <ankur.tyagi85@gmail.com>
>
> Drop patch which is now merged in simdutf[1] v7.7.1 used by vte[2]
>
> [1] https://github.com/simdutf/simdutf/commit/c6f8e887ef51bb80dd978180042b9b9f4f46800f
> [1] https://gitlab.gnome.org/GNOME/vte/-/blob/0.84.0/subprojects/simdutf.wrap?ref_type=tags
>
> Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
> ---
Hi Ankur,
Thanks for your patch.
It looks like we have some build issues, at least on ARM64:
ERROR: vte-0.84.0-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/genericarm64/build/build/tmp/work/armv8a-poky-linux/vte/0.84.0/temp/run.do_compile.515741' failed with exit code 1
...
| FAILED: [code=1] subprojects/simdutf/libsimdutf.a.p/meson-generated_.._simdutf.cpp.o
| aarch64-poky-linux-g++ -march=armv8-a+crc -mbranch-protection=standard -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/srv/pokybuild/yocto-worker/genericarm64/build/build/tmp/work/armv8a-poky-linux/vte/0.84.0/recipe-sysroot -Isubprojects/simdutf/libsimdutf.a.p -Isubprojects/simdutf -I../sources/vte-0.84.0/subprojects/simdutf -fvisibility=hidden -fdiagnostics-color=always -D_GLIBCXX_ASSERTIONS=1 -D_FILE_OFFSET_BITS=64 -std=gnu++23 -O2 -g -fcanon-prefix-map -ffile-prefix-map=/srv/pokybuild/yocto-worker/genericarm64/build/build/tmp/work/armv8a-poky-linux/vte/0.84.0/sources/vte-0.84.0=/usr/src/debug/vte/0.84.0 -ffile-prefix-map=/srv/pokybuild/yocto-worker/genericarm64/build/build/tmp/work/armv8a-poky-linux/vte/0.84.0/build=/usr/src/debug/vte/0.84.0 -ffile-prefix-map=/srv/pokybuild/yocto-worker/genericarm64/build/build/tmp/work/armv8a-poky-linux/vte/0.84.0/recipe-sysroot= -ffile-prefix-map=/srv/pokybuild/yocto-worker/genericarm64/build/build/tmp/work/armv8a-poky-linux/vte/0.84.0/recipe-sysroot-native= -pipe -fvisibility-inlines-hidden -fPIC -isystem../sources/vte-0.84.0/subprojects/simdutf/include -Wno-undef -Wno-missing-declarations -MD -MQ subprojects/simdutf/libsimdutf.a.p/meson-generated_.._simdutf.cpp.o -MF subprojects/simdutf/libsimdutf.a.p/meson-generated_.._simdutf.cpp.o.d -o subprojects/simdutf/libsimdutf.a.p/meson-generated_.._simdutf.cpp.o -c subprojects/simdutf/simdutf.cpp
| subprojects/simdutf/simdutf.cpp:1819:2: error: expected ';' after class definition
| 1819 | } // namespace arm64
| | ^
| | ;
| subprojects/simdutf/simdutf.cpp:11490:52: error: definition of 'bool simdutf::implementation::supported_by_runtime_system() const' is not in namespace enclosing 'simdutf::implementation' [-fpermissive]
| 11490 | bool implementation::supported_by_runtime_system() const {
| | ^~~~~
| subprojects/simdutf/simdutf.cpp:11531:21: error: 'implementation' in namespace 'simdutf::simdutf::arm64' does not name a type
| 11531 | static const arm64::implementation *get_arm64_singleton() {
| | ^~~~~~~~~~~~~~
...
https://autobuilder.yoctoproject.org/valkyrie/#/builders/60/builds/3465
https://autobuilder.yoctoproject.org/valkyrie/#/builders/22/builds/3489
Can you have a look at the issue?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-03-27 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 19:04 [OE-core][PATCH v2] vte: upgrade 0.82.2 -> 0.84.0 ankur.tyagi85
2026-03-27 8:41 ` Mathieu Dubois-Briand [this message]
2026-03-29 0:57 ` Ankur Tyagi
-- strict thread matches above, loose matches on Subject: below --
2026-03-29 0:58 ankur.tyagi85
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=DHDFIRLFWLM2.MENHJ5825HET@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=ankur.tyagi85@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