From: "Jakov Smolić" <jsmolic@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/bpftrace/
Date: Sun,  7 Nov 2021 20:59:42 +0000 (UTC)	[thread overview]
Message-ID: <1636318721.073fb10f6fedaf9dc92fc31edf912e4b5076e00c.jsmolic@gentoo> (raw)
commit:     073fb10f6fedaf9dc92fc31edf912e4b5076e00c
Author:     Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
AuthorDate: Sun Nov  7 20:58:21 2021 +0000
Commit:     Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
CommitDate: Sun Nov  7 20:58:41 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=073fb10f
dev-util/bpftrace: Drop unused toolchain-funcs in 0.13.0-r1 and 0.14.0-r2
Signed-off-by: Jakov Smolić <jsmolic <AT> gentoo.org>
 dev-util/bpftrace/bpftrace-0.13.0-r1.ebuild | 2 +-
 dev-util/bpftrace/bpftrace-0.14.0-r2.ebuild | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-util/bpftrace/bpftrace-0.13.0-r1.ebuild b/dev-util/bpftrace/bpftrace-0.13.0-r1.ebuild
index 3437f2e80ce..bf4eda842df 100644
--- a/dev-util/bpftrace/bpftrace-0.13.0-r1.ebuild
+++ b/dev-util/bpftrace/bpftrace-0.13.0-r1.ebuild
@@ -3,7 +3,7 @@
 
 EAPI=7
 
-inherit toolchain-funcs llvm linux-info cmake
+inherit llvm linux-info cmake
 
 DESCRIPTION="High-level tracing language for eBPF"
 HOMEPAGE="https://github.com/iovisor/bpftrace"
diff --git a/dev-util/bpftrace/bpftrace-0.14.0-r2.ebuild b/dev-util/bpftrace/bpftrace-0.14.0-r2.ebuild
index 483f341c490..bb1d9b9bc09 100644
--- a/dev-util/bpftrace/bpftrace-0.14.0-r2.ebuild
+++ b/dev-util/bpftrace/bpftrace-0.14.0-r2.ebuild
@@ -3,7 +3,7 @@
 
 EAPI=7
 
-inherit toolchain-funcs llvm linux-info cmake
+inherit llvm linux-info cmake
 
 DESCRIPTION="High-level tracing language for eBPF"
 HOMEPAGE="https://github.com/iovisor/bpftrace"
next             reply	other threads:[~2021-11-07 20:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-07 20:59 Jakov Smolić [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-23 18:45 [gentoo-commits] repo/gentoo:master commit in: dev-util/bpftrace/ Jakov Smolić
2023-10-04 17:42 Patrick McLean
2023-04-20 21:09 Patrick McLean
2023-04-12 23:31 Patrick McLean
2023-02-01  1:57 Patrick McLean
2023-01-13 18:40 Patrick McLean
2022-12-07 13:52 David Seifert
2022-10-09 15:07 Yixun Lan
2022-09-27 21:41 Sam James
2022-09-22 20:11 Patrick McLean
2022-08-24 18:20 Patrick McLean
2022-06-27 17:32 Jakov Smolić
2022-02-11 19:53 Jakov Smolić
2022-01-31 19:40 Jakov Smolić
2022-01-06 17:19 Patrick McLean
2021-12-05  3:26 Sam James
2021-11-07 20:59 Jakov Smolić
2021-11-07 20:59 Jakov Smolić
2021-11-07 20:59 Jakov Smolić
2021-11-07 20:59 Jakov Smolić
2021-11-07 20:59 Jakov Smolić
2021-11-07 20:59 Jakov Smolić
2021-04-20  3:30 Patrick McLean
2021-03-24 23:59 Patrick McLean
2020-11-14 19:27 Patrick McLean
2020-11-14  1:30 Patrick McLean
2020-10-30 21:13 Patrick McLean
2020-09-22 19:26 Patrick McLean
2020-08-25  0:19 Patrick McLean
2019-07-31 23:18 Patrick McLean
2019-06-25 18:08 Patrick McLean
2019-06-20 18:25 Patrick McLean
2019-05-21 16:45 Stephen Klimaszewski
2019-04-12  4:31 Patrick McLean
2019-04-12  4:28 Patrick McLean
2019-04-05 18:03 Patrick McLean
2019-03-16 20:43 Patrick McLean
2019-03-16 20:43 Patrick McLean
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=1636318721.073fb10f6fedaf9dc92fc31edf912e4b5076e00c.jsmolic@gentoo \
    --to=jsmolic@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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