public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Michel Lind <salimma@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/retsnoop] rawhide: Apply libbpf ppc64le fix; Fixes: rhbz#2402550
Date: Wed, 22 Jul 2026 12:05:42 GMT [thread overview]
Message-ID: <178472194251.1.16811635837851192530.rpms-retsnoop-9f40a664ae25@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/retsnoop
Branch : rawhide
Commit : 9f40a664ae25a3b5115428ed89a75c429c99a032
Author : Michel Lind <salimma@fedoraproject.org>
Date : 2026-07-22T13:05:18+01:00
Stats : +17/-3 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/retsnoop/c/9f40a664ae25a3b5115428ed89a75c429c99a032?branch=rawhide
Log:
Apply libbpf ppc64le fix; Fixes: rhbz#2402550
Signed-off-by: Michel Lind <salimma@fedoraproject.org>
---
diff --git a/libbpf-fix-ppc-stack-reg-definition.diff b/libbpf-fix-ppc-stack-reg-definition.diff
new file mode 100644
index 0000000..2307050
--- /dev/null
+++ b/libbpf-fix-ppc-stack-reg-definition.diff
@@ -0,0 +1,13 @@
+diff --git a/src/bpf_tracing.h b/src/bpf_tracing.h
+index a8f6cd484..dbe32a5d0 100644
+--- a/src/bpf_tracing.h
++++ b/src/bpf_tracing.h
+@@ -311,7 +311,7 @@ struct pt_regs___arm64 {
+ #define __PT_RET_REG regs[31]
+ #define __PT_FP_REG __unsupported__
+ #define __PT_RC_REG gpr[3]
+-#define __PT_SP_REG sp
++#define __PT_SP_REG gpr[1]
+ #define __PT_IP_REG nip
+
+ #elif defined(bpf_target_sparc)
diff --git a/retsnoop.spec b/retsnoop.spec
index 7f657b0..76d484a 100644
--- a/retsnoop.spec
+++ b/retsnoop.spec
@@ -47,15 +47,15 @@ Source3: README.Fedora
# (Without changes to Cargo.lock)
Patch: retsnoop-0.11-gimli-0.32-etc.patch
+# needs to be applied after we unpack libbpf
+Source4: https://github.com/libbpf/libbpf/commit/99bf90957ae767842646effa29da8c9a9ecdb696.diff#/libbpf-fix-ppc-stack-reg-definition.diff
+
# has a Rust component
ExclusiveArch: %{rust_arches}
# bpftool not compiling on ix86
# we don't ship 32-bit binaries anyway, but it'd be good to test compilation
# once this is fixed https://github.com/libbpf/bpftool/issues/158
ExcludeArch: %{ix86}
-# retsnoop 0.11 FTBFS on ppc64le
-# rhbz#2402550
-ExcludeArch: ppc64le
BuildRequires: cargo-rpm-macros >= 24
BuildRequires: clang
@@ -90,6 +90,7 @@ mv libbpf-%{libbpf_commit} libbpf
mv libbpf/LICENSE libbpf-LICENSE
mv libbpf/LICENSE.BSD-2-Clause libbpf-LICENSE.BSD-2-Clause
mv libbpf/LICENSE.LGPL-2.1 libbpf-LICENSE.LGPL-2.1
+(cd libbpf && cat %{SOURCE4} | patch -p1)
# README.Fedora
cp -p %{SOURCE3} .
reply other threads:[~2026-07-22 12:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178472194251.1.16811635837851192530.rpms-retsnoop-9f40a664ae25@fedoraproject.org \
--to=salimma@fedoraproject.org \
--cc=git-commits@fedoraproject.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