public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/google-perftools/
Date: Fri,  2 Sep 2022 21:28:39 +0000 (UTC)	[thread overview]
Message-ID: <1662154108.5564ef5a3056127e1444edd89b45f6e16b560a82.sam@gentoo> (raw)

commit:     5564ef5a3056127e1444edd89b45f6e16b560a82
Author:     dante-robinson <danterobinson2000 <AT> gmail <DOT> com>
AuthorDate: Tue Aug 16 20:36:01 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Sep  2 21:28:28 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5564ef5a

dev-util/google-perftools: add llvm-libunwind to be used

- USE llvm-libunwind

Signed-off-by: dante-robinson <danterobinson2000 <AT> gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/26885
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-util/google-perftools/Manifest                         |  2 +-
 ...rftools-2.10.ebuild => google-perftools-2.10-r1.ebuild} | 14 ++++++--------
 2 files changed, 7 insertions(+), 9 deletions(-)

diff --git a/dev-util/google-perftools/Manifest b/dev-util/google-perftools/Manifest
index 0f343649601f..4957d61fd891 100644
--- a/dev-util/google-perftools/Manifest
+++ b/dev-util/google-perftools/Manifest
@@ -1,2 +1,2 @@
-DIST gperftools-2.9.1.tar.gz 924910 BLAKE2B fcf0491e42ff4212a63ab0af422f27f5a625c53a0b33e69f8dede96b004a0f01af104d9791a4b75d38145ae0059f5e2967ea1d09b0712cc4d930ef7aafd4f3ba SHA512 5e07f28da9afc5f1ba3df7f06ad0e146c171d33e1779bbaab21547ed234aaced02e5278c1eb8f92fc45480abd2474d6a2d4c71644fb9378f41088c56cc1bc8ab
 DIST gperftools-2.10.tar.gz 926512 BLAKE2B e92fb751f9e695d21edf5fce443f3d3641fcff15cbd6b5d868bc77fbe622594be824b75c8d45513c7f82b9e574c690133b8502d4574162948a77886d5166b92d SHA512 4400711723be9401f519d85b3b69c026e4715473cbed48ab0573df17abdf895fb971ee969875fe5127a2e8b9aba90d858285e50c8e012384c2c36d5a76b1f0c4
+DIST gperftools-2.9.1.tar.gz 924910 BLAKE2B fcf0491e42ff4212a63ab0af422f27f5a625c53a0b33e69f8dede96b004a0f01af104d9791a4b75d38145ae0059f5e2967ea1d09b0712cc4d930ef7aafd4f3ba SHA512 5e07f28da9afc5f1ba3df7f06ad0e146c171d33e1779bbaab21547ed234aaced02e5278c1eb8f92fc45480abd2474d6a2d4c71644fb9378f41088c56cc1bc8ab

diff --git a/dev-util/google-perftools/google-perftools-2.10.ebuild b/dev-util/google-perftools/google-perftools-2.10-r1.ebuild
similarity index 88%
rename from dev-util/google-perftools/google-perftools-2.10.ebuild
rename to dev-util/google-perftools/google-perftools-2.10-r1.ebuild
index 42f067fa0ced..cb76ce6b7b1d 100644
--- a/dev-util/google-perftools/google-perftools-2.10.ebuild
+++ b/dev-util/google-perftools/google-perftools-2.10-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2021 Gentoo Authors
+# Copyright 1999-2022 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
@@ -19,16 +19,14 @@ SLOT="0/4"
 # AIX ppc/ppc64
 KEYWORDS="-* ~amd64 ~arm ~arm64 ~ppc ~ppc64 ~riscv ~x86 ~amd64-linux ~x86-linux"
 
-IUSE="largepages largepages64k +debug minimal optimisememory test static-libs"
+IUSE="largepages largepages64k +debug llvm-libunwind minimal optimisememory test static-libs"
 
 RESTRICT="!test? ( test )"
 
-# TODO: remove the riscv special case once either libunwind has begun supporting this arch
-# or this package allows using llvm-libunwind for other arches
-DEPEND="!ppc64? (
-	riscv? ( sys-libs/llvm-libunwind:= )
-	!riscv? ( sys-libs/libunwind:= )
-)"
+DEPEND="
+	llvm-libunwind? ( sys-libs/llvm-libunwind:= )
+	!llvm-libunwind? ( sys-libs/libunwind:= )
+"
 RDEPEND="${DEPEND}"
 
 S="${WORKDIR}/${MY_P}"


             reply	other threads:[~2022-09-02 21:28 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-02 21:28 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-20 23:40 [gentoo-commits] repo/gentoo:master commit in: dev-util/google-perftools/ Bernard Cafarelli
2024-10-04 14:49 Bernard Cafarelli
2024-10-04 14:49 Bernard Cafarelli
2024-06-20 20:11 Arthur Zamarin
2024-06-20 20:11 Arthur Zamarin
2024-06-20 20:10 Arthur Zamarin
2024-06-20 20:10 Arthur Zamarin
2024-06-20 18:06 Sam James
2024-06-19 19:43 Arthur Zamarin
2024-03-02 22:16 Bernard Cafarelli
2024-03-02 13:22 Arthur Zamarin
2024-02-24 10:20 Bernard Cafarelli
2024-02-17 14:48 Sam James
2024-02-15 20:50 Bernard Cafarelli
2024-02-15 20:03 Sam James
2024-02-15 20:03 Sam James
2024-02-15 18:34 Jakov Smolić
2024-02-15 18:34 Jakov Smolić
2024-02-15 13:11 Bernard Cafarelli
2022-07-15  1:32 Sam James
2021-10-27 22:54 Sam James
2021-10-27 22:47 Sam James
2021-10-27 22:47 Sam James
2021-10-27 22:35 Sam James
2021-10-27 22:35 Sam James
2021-10-27 22:33 Sam James
2021-10-27  5:37 Sam James
2021-10-27  5:34 Sam James
2021-07-11 22:02 Marek Szuba
2021-07-11 22:02 Marek Szuba
2021-06-15 18:47 Georgy Yakovlev
2020-08-21  6:13 Georgy Yakovlev
2020-08-21  3:12 Georgy Yakovlev
2020-06-06 17:38 Agostino Sarubbo
2020-06-06 17:34 Agostino Sarubbo
2020-06-06 17:32 Agostino Sarubbo
2020-06-06 17:29 Agostino Sarubbo
2020-06-06 17:27 Agostino Sarubbo
2020-06-06  8:33 Georgy Yakovlev
2020-06-06  7:36 Georgy Yakovlev
2020-04-15  4:29 Georgy Yakovlev
2020-04-15  2:42 Georgy Yakovlev
2020-04-15  2:42 Georgy Yakovlev
2020-02-09 13:14 David Seifert
2019-04-25  3:52 Aaron Bauman
2018-10-14 11:40 Pacho Ramos
2018-10-14 10:18 Pacho Ramos
2018-01-23  5:58 Markus Meier
2017-12-19  3:09 Lars Wendler
2017-12-19  3:09 Lars Wendler
2017-12-15  9:36 Jason Zaman
2017-12-09 14:54 Sergei Trofimovich
2017-12-08 21:58 Thomas Deutschmann
2017-12-01  5:08 Zac Medico
2017-08-10 15:49 Guilherme Amadio
2017-07-30 20:31 Patrick McLean
2017-07-30 20:31 Patrick McLean
2017-07-29 23:24 Patrick McLean
2017-07-07 18:15 Alexis Ballier
2017-02-15 23:14 Michael Weber
2016-12-29  4:12 Göktürk Yüksek
2016-09-27  7:57 Michał Górny
2016-06-08  6:29 Yixun Lan
2015-09-21  4:58 Jeroen Roovers
2015-09-01 19:31 Tobias Klausmann

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=1662154108.5564ef5a3056127e1444edd89b45f6e16b560a82.sam@gentoo \
    --to=sam@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