From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libsecp256k1/
Date: Sun, 14 May 2023 17:11:15 +0000 (UTC) [thread overview]
Message-ID: <1684084240.3e5707be91c67a3cca2c32ff31e27843c32f8a74.sam@gentoo> (raw)
commit: 3e5707be91c67a3cca2c32ff31e27843c32f8a74
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun May 14 17:01:14 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun May 14 17:10:40 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3e5707be
dev-libs/libsecp256k1: defer to new global USE=valgrind description
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-libs/libsecp256k1/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/dev-libs/libsecp256k1/metadata.xml b/dev-libs/libsecp256k1/metadata.xml
index 9a105e32f61a..b417343b1b53 100644
--- a/dev-libs/libsecp256k1/metadata.xml
+++ b/dev-libs/libsecp256k1/metadata.xml
@@ -19,7 +19,6 @@
<flag name="recovery">Enable ECDSA pubkey recovery module</flag>
<flag name="schnorr">Enable Schnorr signature module</flag>
<flag name="test-openssl">Enable OpenSSL comparison tests</flag>
- <flag name="valgrind">Compile in valgrind memory hints</flag>
</use>
<upstream>
<remote-id type="github">bitcoin/secp256k1</remote-id>
next reply other threads:[~2023-05-14 17:11 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 17:11 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-10 6:54 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libsecp256k1/ Arthur Zamarin
2024-08-25 15:24 Andreas K. Hüttel
2024-08-13 7:36 Joonas Niilola
2024-08-13 7:36 Joonas Niilola
2024-05-08 20:48 Florian Schmaus
2024-05-08 20:48 Florian Schmaus
2024-01-21 17:09 Sam James
2023-10-24 9:14 Joonas Niilola
2023-10-24 9:14 Joonas Niilola
2023-09-18 9:01 Sam James
2023-05-14 7:51 Sam James
2023-04-11 4:07 Sam James
2023-03-13 18:07 Sam James
2023-03-13 18:07 Sam James
2023-01-07 7:41 Sam James
2023-01-07 7:41 Sam James
2023-01-07 7:41 Sam James
2023-01-07 7:41 Sam James
2023-01-06 12:43 Sam James
2021-05-28 3:17 Sam James
2021-05-28 2:27 Sam James
2021-02-07 9:03 Joonas Niilola
2021-02-07 9:03 Joonas Niilola
2021-01-21 23:41 Sam James
2020-08-30 17:14 Thomas Deutschmann
2020-08-29 13:23 Sam James
2020-05-01 15:09 Joonas Niilola
2019-10-13 11:22 Joonas Niilola
2019-10-13 11:22 Joonas Niilola
2019-10-13 11:22 Joonas Niilola
2019-01-11 21:38 Craig Andrews
2017-01-05 14:12 Anthony G. Basile
2016-12-20 9:08 Agostino Sarubbo
2016-12-19 19:56 Tobias Klausmann
2016-06-26 0:09 Anthony G. Basile
2016-03-20 15:42 Anthony G. Basile
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=1684084240.3e5707be91c67a3cca2c32ff31e27843c32f8a74.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