diff --git a/meta/recipes-kernel/systemtap/systemtap/0001-python3.stpm-record-the-installed-libpython-path.patch b/meta/recipes-kernel/systemtap/systemtap/0001-python3.stpm-record-the-installed-libpython-path.patch index 93efec941b..9759434521 100644 --- a/meta/recipes-kernel/systemtap/systemtap/0001-python3.stpm-record-the-installed-libpython-path.patch +++ b/meta/recipes-kernel/systemtap/systemtap/0001-python3.stpm-record-the-installed-libpython-path.patch @@ -1,33 +1,26 @@ -From 0387b9416ad7c25d71685441e1046f1c72cb1d42 Mon Sep 17 00:00:00 2001 +From b9bd609254f54fedba0b7155c63a3b3f6d84993c Mon Sep 17 00:00:00 2001 From: Jaipaul Cheernam -Date: Sat, 19 Sep 2026 13:12:44 +0000 -Subject: [PATCH 1/2] python3.stpm: record the installed libpython path +Date: Wed, 23 Sep 2026 18:52:56 -0400 +Subject: [PATCH] PR34652: python3.stpm: record the installed libpython path tapset/python3.stpm is generated at build time and installed, and its -stap_python3_libpython macro is the module argument of the @cast()s in -tapset/python3.stp: +stap_python3_libpython macro is the module argument of the @cast()s +in tapset/python3.stp. @cast module names are taken literally, so +the macro has to name libpython as it exists on the machine stap is +tracing. - @cast(@object, "PyFrameObject", @stap_python3_libpython) +configure instead derives it from sysconfig's LIBDIR for the +interpreter that built HelperSDT. When cross compiling that is a +directory in the build host's staging area, which exists on no +machine but the builder, so every python3 probe on the installed +system fails to resolve PyFrameObject. -@cast module names are taken literally -- dwarf_cast_expanding_visitor -resolves them with find_executable(module, "", sess.sysenv), i.e. with no -sysroot translation -- so the macro has to name libpython as it exists on -the machine stap is tracing. +Keep only the library soname from sysconfig and anchor it at the +$(libdir) being installed into, so the macro names the installed +library. For a native build where the interpreter's LIBDIR is +$(libdir) the generated value is unchanged. -configure instead derives it from sysconfig's LIBDIR for the interpreter -that built HelperSDT. When cross compiling that is a directory in the -build host's staging area, which exists on no machine but the builder, so -every python3 probe on the installed system fails to resolve -PyFrameObject. The installed file also ends up carrying a build -directory, which distro QA checks reject (OpenEmbedded's buildpaths test -flags it as a packaging error). - -Keep only the library soname from sysconfig and anchor it at the $(libdir) -being installed into, so the macro names the installed library. For a -native build where the interpreter's LIBDIR is $(libdir) -- the usual case --- the generated value is unchanged. - -Upstream-Status: Submitted [https://inbox.sourceware.org/systemtap/20260919135744.78642-2-jaipaul.cheernam@est.tech/] +Upstream-Status: Backport [https://sourceware.org/git/?p=systemtap.git;a=commit;h=b9bd609254f54fedba0b7155c63a3b3f6d84993c] Signed-off-by: Jaipaul Cheernam --- Makefile.am | 10 +++++++++-