Skip to contentSkip to conversation

vte: Upgrade to 0.78.0

PATCH Superseded Khem Raj 2 participants 5 messages Sep 23, 2024 – Sep 24, 2024

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore

Khem Raj

author
#0 lore raw

PATCH 1/1 vte: Upgrade to 0.78.0

- Needed for Gnome-47 components e.g. gnome-console
- Disable GI_DATA on arm, it uses qemu usermode and qemu-user crashes while running qemu_Vte-3.91

---
 meta/recipes-support/vte/{vte_0.76.3.bb => vte_0.78.0.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-support/vte/{vte_0.76.3.bb => vte_0.78.0.bb} (94%)
meta/recipes-support/vte/vte_0.78.0.bb renamed from meta/recipes-support/vte/vte_0.76.3.bb +2 -2
similarity index 94%
rename from meta/recipes-support/vte/vte_0.76.3.bb
rename to meta/recipes-support/vte/vte_0.78.0.bb
index 515ff228fd4..f44d39ac451 100644
@@ -15,11 +15,11 @@ DEPENDS = "glib-2.0 glib-2.0-native gtk+3 libpcre2 libxml2-native gperf-native i
 
 GIR_MESON_OPTION = 'gir'
 GIDOCGEN_MESON_OPTION = "docs"
-
+GI_DATA_ENABLED:armv7ve = "False"
 inherit gnomebase gi-docgen features_check upstream-version-is-even gobject-introspection systemd vala
 
 SRC_URI += "file://0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch"
-SRC_URI[archive.sha256sum] = "f678e94c056f377fd0021214adff5450cb172e9a08b160911181ddff7b7d5d60"
+SRC_URI[archive.sha256sum] = "07f09c6228a8bb3c1599dd0f5a6ec797b30d3010c3ac91cf21b69d9635dfaf7c"
 
 ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"
 
#1 lore raw

How can the crash be reproduced? This must be specified. Could it be specific to your setup? Qemu usermode is pretty robust with standard poky.

Alex

Quoted 48 lines · Khem Raj via lists.openembedded.org

- Needed for Gnome-47 components e.g. gnome-console
- Disable GI_DATA on arm, it uses qemu usermode and qemu-user crashes while running qemu_Vte-3.91

---
 meta/recipes-support/vte/{vte_0.76.3.bb => vte_0.78.0.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-support/vte/{vte_0.76.3.bb => vte_0.78.0.bb} (94%)
meta/recipes-support/vte/vte_0.78.0.bb renamed from meta/recipes-support/vte/vte_0.76.3.bb +0 -0
similarity index 94%
rename from meta/recipes-support/vte/vte_0.76.3.bb
rename to meta/recipes-support/vte/vte_0.78.0.bb
index 515ff228fd4..f44d39ac451 100644
@@ -15,11 +15,11 @@ DEPENDS = "glib-2.0 glib-2.0-native gtk+3 libpcre2

libxml2-native gperf-native i

GIR_MESON_OPTION = 'gir'
GIDOCGEN_MESON_OPTION = "docs"

meta/recipes-support/vte/vte_0.78.0.bb renamed from meta/recipes-support/vte/vte_0.76.3.bb +1 -1
-
+GI_DATA_ENABLED:armv7ve = "False"
 inherit gnomebase gi-docgen features_check upstream-version-is-even

gobject-introspection systemd vala

SRC_URI += "file://0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch"
-SRC_URI[archive.sha256sum] = "f678e94c056f377fd0021214adff5450cb172e9a08b160911181ddff7b7d5d60" +SRC_URI[archive.sha256sum] = "07f09c6228a8bb3c1599dd0f5a6ec797b30d3010c3ac91cf21b69d9635dfaf7c"

ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#204827):
https://lists.openembedded.org/g/openembedded-core/message/204827
Mute This Topic: https://lists.openembedded.org/mt/108619476/1686489
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

author
#2 lore raw
Quoted 3 lines · Alexander Kanavin

How can the crash be reproduced? This must be specified. Could it be specific to your setup? Qemu usermode is pretty robust with standard poky.

It could be my setup but I could see it with clang and gcc and I left it there. Its a bit convoluted to reproduce since its in generated program which is called via another wrapper over qemu usermode,
here is the cmdline which can be used. After do_compile task is run for vte.
https://snips.sh/f/sREktUGD0f

Quoted 44 lines

Alex

Quoted 41 lines · Khem Raj via lists.openembedded.org

- Needed for Gnome-47 components e.g. gnome-console
- Disable GI_DATA on arm, it uses qemu usermode and qemu-user crashes while running qemu_Vte-3.91

---
 meta/recipes-support/vte/{vte_0.76.3.bb => vte_0.78.0.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-support/vte/{vte_0.76.3.bb => vte_0.78.0.bb} (94%)
meta/recipes-support/vte/vte_0.78.0.bb renamed from meta/recipes-support/vte/vte_0.76.3.bb +2 -3
similarity index 94%
rename from meta/recipes-support/vte/vte_0.76.3.bb
rename to meta/recipes-support/vte/vte_0.78.0.bb
index 515ff228fd4..f44d39ac451 100644
@@ -15,11 +15,11 @@ DEPENDS = "glib-2.0 glib-2.0-native gtk+3 libpcre2 libxml2-native gperf-native i
 
 GIR_MESON_OPTION = 'gir'
 GIDOCGEN_MESON_OPTION = "docs"
-
+GI_DATA_ENABLED:armv7ve = "False"
 inherit gnomebase gi-docgen features_check upstream-version-is-even gobject-introspection systemd vala
 
 SRC_URI += "file://0001-Add-W_EXITCODE-macro-for-non-glibc-systems.patch"
-SRC_URI[archive.sha256sum] = "f678e94c056f377fd0021214adff5450cb172e9a08b160911181ddff7b7d5d60"
+SRC_URI[archive.sha256sum] = "07f09c6228a8bb3c1599dd0f5a6ec797b30d3010c3ac91cf21b69d9635dfaf7c"
 
 ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"
 
 
-=-=-=-=-=-=-=-=-=-=-=-

Links: You receive all messages sent to this group.
View/Reply Online (#204827): https://lists.openembedded.org/g/openembedded-core/message/204827
Mute This Topic: https://lists.openembedded.org/mt/108619476/1686489
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#3 lore raw
Quoted 7 lines · Khem Raj
Quoted 2 lines

How can the crash be reproduced? This must be specified. Could it be specific to your setup? Qemu usermode is pretty robust with standard poky.

It could be my setup but I could see it with clang and gcc and I left it there. Its a bit convoluted to reproduce since its in generated program which is called via another wrapper over qemu usermode,
here is the cmdline which can be used. After do_compile task is run for vte.
https://snips.sh/f/sREktUGD0f

I think it is your setup. I just built this update on poky qemuarm with g-i re-enabled, and it worked (both glibc and musl). So you need to narrow it down to something else, disabling it for everyone isn't correct.

Alex

author
#4 lore raw
Quoted 9 lines · Alexander Kanavin
Quoted 1 line · Khem Raj
Quoted 1 line

How can the crash be reproduced? This must be specified. Could it be

specific to your setup? Qemu usermode is pretty robust with standard poky.

Quoted 2 lines
Quoted 1 line

It could be my setup but I could see it with clang and gcc and I left it

there.

Quoted 3 lines

Its a bit convoluted to reproduce since its in generated program which is called via another wrapper over qemu usermode,
here is the cmdline which can be used. After do_compile task is run for

Quoted 7 lines

vte.

Quoted 1 line

https://snips.sh/f/sREktUGD0f

I think it is your setup. I just built this update on poky qemuarm with g-i re-enabled, and it worked (both glibc and musl). So you need to narrow it down to something else, disabling it for everyone isn't correct.

Thanks will send a v2

Quoted 3 lines

Alex