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-cpp/folly/
Date: Mon,  7 Mar 2022 07:31:00 +0000 (UTC)	[thread overview]
Message-ID: <1646638249.645f50f395cc89de20897fcd27d6d5414cf183af.sam@gentoo> (raw)

commit:     645f50f395cc89de20897fcd27d6d5414cf183af
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Mar  7 07:30:21 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Mar  7 07:30:49 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=645f50f3

dev-cpp/folly: BDEPEND on Clang for tests

Did this in one of the other ebuilds (which I ended up
not committing for now as unneeded deps) but not this one
apparently. Oops.

Closes: https://bugs.gentoo.org/834703
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-cpp/folly/folly-2022.02.28.00.ebuild | 1 +
 1 file changed, 1 insertion(+)

diff --git a/dev-cpp/folly/folly-2022.02.28.00.ebuild b/dev-cpp/folly/folly-2022.02.28.00.ebuild
index d9c4c5003e07..b644181fecc6 100644
--- a/dev-cpp/folly/folly-2022.02.28.00.ebuild
+++ b/dev-cpp/folly/folly-2022.02.28.00.ebuild
@@ -36,6 +36,7 @@ RDEPEND="app-arch/bzip2
 # libiberty is linked statically
 DEPEND="${RDEPEND}
 	sys-libs/binutils-libs"
+BDEPEND="test? ( sys-devel/clang )"
 
 pkg_setup() {
 	if use test && [[ ${BUILD_TYPE} != "binary" ]] && ! tc-is-clang ; then


             reply	other threads:[~2022-03-07  7:31 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07  7:31 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-01 11:47 [gentoo-commits] repo/gentoo:master commit in: dev-cpp/folly/ Sam James
2024-12-01 11:47 Sam James
2024-11-23 20:16 Sam James
2024-11-23 14:01 Sam James
2024-11-23 14:01 Sam James
2024-11-15  9:51 Petr Vaněk
2024-11-11 22:25 Sam James
2023-06-24  8:29 Arthur Zamarin
2023-06-24  6:32 Sam James
2023-06-24  5:39 Sam James
2023-05-04  9:03 Sam James
2023-05-01  1:43 Sam James
2023-04-14  3:39 Sam James
2023-02-17  8:59 Sam James
2023-02-16  3:29 Sam James
2023-02-06 21:25 Sam James
2023-01-23 20:25 Sam James
2022-12-21 22:54 Sam James
2022-12-16 20:48 Arthur Zamarin
2022-09-18  0:35 Sam James
2022-09-18  0:35 Sam James
2022-09-06  4:18 Sam James
2022-08-29 20:13 Sam James
2022-08-23  3:51 Sam James
2022-08-23  3:30 Sam James
2022-08-15 18:19 Sam James
2022-08-13 15:09 Sam James
2022-08-13 15:09 Sam James
2022-07-09  4:25 Sam James
2022-07-08  0:57 Sam James
2022-05-16 12:51 Agostino Sarubbo
2022-04-17 16:44 Sam James
2022-04-16  3:07 Sam James
2022-04-05  3:08 Sam James
2022-04-05  3:08 Sam James
2022-04-01  3:53 Sam James
2022-04-01  3:53 Sam James
2022-03-22  1:48 Sam James
2022-03-18  6:16 Sam James
2022-03-09 15:34 Sam James
2022-03-07  3:24 Sam James

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=1646638249.645f50f395cc89de20897fcd27d6d5414cf183af.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