From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-misc/hashcash/
Date: Fri, 21 Oct 2022 12:48:25 +0000 (UTC) [thread overview]
Message-ID: <1666356422.5e271b86edf8e01a35bcc9befe76f134892f13ed.ionen@gentoo> (raw)
commit: 5e271b86edf8e01a35bcc9befe76f134892f13ed
Author: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Fri Oct 21 12:23:28 2022 +0000
Commit: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Fri Oct 21 12:47:02 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5e271b86
net-misc/hashcash: drop c2x workaround
Changed the way test for this, and upon closer look
this one wasn't needed.
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>
net-misc/hashcash/hashcash-1.22-r2.ebuild | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/net-misc/hashcash/hashcash-1.22-r2.ebuild b/net-misc/hashcash/hashcash-1.22-r2.ebuild
index 55d0da7126d5..c52b23016a1b 100644
--- a/net-misc/hashcash/hashcash-1.22-r2.ebuild
+++ b/net-misc/hashcash/hashcash-1.22-r2.ebuild
@@ -3,7 +3,7 @@
EAPI=8
-inherit flag-o-matic toolchain-funcs
+inherit toolchain-funcs
DESCRIPTION="Utility to generate hashcash tokens"
HOMEPAGE="http://www.hashcash.org"
@@ -25,7 +25,6 @@ src_prepare() {
src_compile() {
tc-export AR CC
- append-cflags -std=gnu89 # old codebase, incompatible with c2x
emake generic
}
next reply other threads:[~2022-10-21 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 12:48 Ionen Wolkens [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-11 8:56 [gentoo-commits] repo/gentoo:master commit in: net-misc/hashcash/ Ionen Wolkens
2022-09-28 2:35 Ionen Wolkens
2022-06-05 11:53 Matthew Smith
2022-02-13 21:08 Conrad Kostecki
2019-10-12 8:04 Michał Górny
2019-10-11 13:48 Joonas Niilola
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=1666356422.5e271b86edf8e01a35bcc9befe76f134892f13ed.ionen@gentoo \
--to=ionen@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