From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/gpgstats/
Date: Tue, 14 Feb 2023 23:04:28 +0000 (UTC) [thread overview]
Message-ID: <1676415832.adea75f20d8c06b9708d5a7d6f53a07d91360c7d.sam@gentoo> (raw)
commit: adea75f20d8c06b9708d5a7d6f53a07d91360c7d
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Feb 14 23:00:49 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Feb 14 23:03:52 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=adea75f2
app-crypt/gpgstats: fix build w/ clang 16
No patch as upstream is 404, apparently.
Closes: https://bugs.gentoo.org/894350
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-crypt/gpgstats/gpgstats-0.5-r2.ebuild | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/app-crypt/gpgstats/gpgstats-0.5-r2.ebuild b/app-crypt/gpgstats/gpgstats-0.5-r2.ebuild
index 85f24aeaccea..860db1e0ed25 100644
--- a/app-crypt/gpgstats/gpgstats-0.5-r2.ebuild
+++ b/app-crypt/gpgstats/gpgstats-0.5-r2.ebuild
@@ -1,9 +1,9 @@
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2023 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
-inherit toolchain-funcs
+inherit flag-o-matic toolchain-funcs
DESCRIPTION="GPGstats calculates statistics on the keys in your key-ring"
HOMEPAGE="http://www.vanheusden.com/gpgstats/"
@@ -19,6 +19,9 @@ DEPEND="${RDEPEND}"
PATCHES=( "${FILESDIR}"/${P}-flags.patch )
src_compile() {
+ # Uses removed 'register' keyword, bug #894350
+ append-cxxflags -std=c++14
+
emake CC="$(tc-getCC)" CXX="$(tc-getCXX)" DEBUG=
}
next reply other threads:[~2023-02-14 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 23:04 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-16 22:33 [gentoo-commits] repo/gentoo:master commit in: app-crypt/gpgstats/ David Seifert
2017-03-25 21:46 Alon Bar-Lev
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=1676415832.adea75f20d8c06b9708d5a7d6f53a07d91360c7d.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