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-libs/mimalloc/
Date: Tue, 16 May 2023 01:52:55 +0000 (UTC)	[thread overview]
Message-ID: <1684201936.4d42d6b4c812913a48b3757c58748fd65d87006d.sam@gentoo> (raw)

commit:     4d42d6b4c812913a48b3757c58748fd65d87006d
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue May 16 00:48:43 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue May 16 01:52:16 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4d42d6b4

dev-libs/mimalloc: add Valgrind annotation support

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-libs/mimalloc/mimalloc-2.1.2.ebuild | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/dev-libs/mimalloc/mimalloc-2.1.2.ebuild b/dev-libs/mimalloc/mimalloc-2.1.2.ebuild
index a81b2c3128af..362471406fc9 100644
--- a/dev-libs/mimalloc/mimalloc-2.1.2.ebuild
+++ b/dev-libs/mimalloc/mimalloc-2.1.2.ebuild
@@ -12,9 +12,11 @@ SRC_URI="https://github.com/microsoft/mimalloc/archive/refs/tags/v${PV}.tar.gz -
 LICENSE="MIT"
 SLOT="0/2"
 KEYWORDS="~amd64 ~arm64 ~loong ~ppc64 ~riscv ~x86"
-IUSE="hardened test"
+IUSE="hardened test valgrind"
 RESTRICT="!test? ( test )"
 
+DEPEND="valgrind? ( dev-util/valgrind )"
+
 src_configure() {
 	local mycmakeargs=(
 		-DMI_SECURE=$(usex hardened)
@@ -23,6 +25,7 @@ src_configure() {
 
 		-DMI_BUILD_OBJECT=OFF
 		-DMI_BUILD_STATIC=OFF
+		-DMI_TRACK_VALGRIND=$(usex valgrind)
 	)
 
 	cmake-multilib_src_configure


             reply	other threads:[~2023-05-16  1:52 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16  1:52 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-05 12:02 [gentoo-commits] repo/gentoo:master commit in: dev-libs/mimalloc/ Arthur Zamarin
2024-08-29  5:10 Jakov Smolić
2024-08-12 18:53 Sam James
2024-07-14 10:41 James Le Cuirot
2024-06-02  5:46 Sam James
2024-05-20  8:11 Sam James
2024-05-20  8:11 Sam James
2024-04-23 17:36 Matthew Smith
2024-01-29  9:33 Matthew Smith
2023-11-25  5:28 Sam James
2023-11-13  4:35 Sam James
2023-11-13  4:35 Sam James
2023-06-25  7:05 Sam James
2023-04-25 14:02 Arthur Zamarin
2023-04-25  1:57 Sam James
2023-04-05 19:32 Georgy Yakovlev
2023-04-03 19:47 Georgy Yakovlev
2023-03-31 21:28 Sam James
2023-03-31 21:28 Sam James
2023-03-04  8:55 Arthur Zamarin
2023-01-27  6:27 Sam James
2023-01-23  7:25 Georgy Yakovlev
2022-12-30  7:32 Sam James
2022-11-15 20:19 Matthew Smith
2022-07-28 10:17 Sam James
2022-07-10  8:40 Matthew Smith
2022-05-28 10:03 Jakov Smolić
2022-05-24 16:07 WANG Xuerui
2022-04-17 16:44 Sam James
2022-04-16  3:07 Sam James
2022-04-13  9:44 Jakov Smolić
2022-04-05  5:27 Agostino Sarubbo
2022-03-14 12:26 Sam James
2022-03-12 17:37 Matthew Smith
2022-03-12 17:37 Matthew Smith
2022-03-12 17:37 Matthew Smith
2022-03-07 19:51 Patrick McLean
2022-02-20  5:51 Sam James
2022-02-18  0:40 Sam James
2022-02-18  0:40 Sam James
2022-01-01  9:39 Sam James
2021-12-20  5:08 Sam James
2021-12-20  4:44 Sam James
2021-12-15  5:42 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=1684201936.4d42d6b4c812913a48b3757c58748fd65d87006d.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