From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] bpftrace: drop 32-bit architectures
Date: Fri, 08 May 2020 21:50:01 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21759@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 325 bytes --]
There is a new pull request by abenson against master on the void-packages repository
https://github.com/abenson/void-packages fix_bpftrace
https://github.com/void-linux/void-packages/pull/21759
bpftrace: drop 32-bit architectures
A patch file from https://github.com/void-linux/void-packages/pull/21759.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fix_bpftrace-21759.patch --]
[-- Type: text/x-diff, Size: 893 bytes --]
From 3e0bc65fff94b707accab14d8e74644bd5d1bf0e Mon Sep 17 00:00:00 2001
From: Andrew Benson <abenson+void@gmail.com>
Date: Fri, 8 May 2020 14:49:39 -0500
Subject: [PATCH] bpftrace: drop 32-bit architectures
---
srcpkgs/bpftrace/template | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/srcpkgs/bpftrace/template b/srcpkgs/bpftrace/template
index b2dccc88932d..8e18639c8af2 100644
--- a/srcpkgs/bpftrace/template
+++ b/srcpkgs/bpftrace/template
@@ -13,6 +13,10 @@ homepage="https://github.com/iovisor/bpftrace/"
distfiles="https://github.com/iovisor/bpftrace/archive/v${version}.tar.gz"
checksum=50ea80c0e337c4aaa260911e013b92ae09bdd5a062b23eb748290409bc2844db
+if [ $XBPS_TARGET_WORDSIZE = 32 ]; then
+ broken="https://github.com/iovisor/bpftrace/commit/4ae387f06fdd133e49a012b3b76623012ba39973"
+fi
+
post_install() {
# clashes with bcc-tools
rm -rf ${DESTDIR}/usr/share/man
next reply other threads:[~2020-05-08 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 19:50 abenson [this message]
2020-05-08 21:38 ` abenson
2020-05-08 21:38 ` [PR PATCH] [Closed]: " abenson
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21759@inbox.vuxu.org \
--to=abenson@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).