From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-cpp/benchmark/files/, dev-cpp/benchmark/
Date: Mon, 11 Jan 2021 17:47:43 +0000 (UTC) [thread overview]
Message-ID: <1610387125.4add4f893cf2fb16b18d3c15bc9948a80802b66f.slyfox@gentoo> (raw)
commit: 4add4f893cf2fb16b18d3c15bc9948a80802b66f
Author: William Breathitt Gray <vilhelm.gray <AT> gmail <DOT> com>
AuthorDate: Sat Jan 9 21:37:54 2021 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Mon Jan 11 17:45:25 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4add4f89
dev-cpp/benchmark: Add patch to fix build failure on gcc-11
Closes: https://bugs.gentoo.org/764647
Signed-off-by: William Breathitt Gray <vilhelm.gray <AT> gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/19012
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
dev-cpp/benchmark/benchmark-1.5.2.ebuild | 4 +++
...chmark-1.5.2-Add-missing-limits-inclusion.patch | 30 ++++++++++++++++++++++
2 files changed, 34 insertions(+)
diff --git a/dev-cpp/benchmark/benchmark-1.5.2.ebuild b/dev-cpp/benchmark/benchmark-1.5.2.ebuild
index 396642b38c3..e3a3e8cfb6e 100644
--- a/dev-cpp/benchmark/benchmark-1.5.2.ebuild
+++ b/dev-cpp/benchmark/benchmark-1.5.2.ebuild
@@ -15,6 +15,10 @@ KEYWORDS="~amd64 ~arm64 ~ppc64 ~x86"
IUSE="test"
RESTRICT="!test? ( test )"
+PATCHES=(
+ "${FILESDIR}/${P}-Add-missing-limits-inclusion.patch"
+)
+
src_configure() {
local mycmakeargs=(
-DBENCHMARK_ENABLE_TESTING=$(usex test)
diff --git a/dev-cpp/benchmark/files/benchmark-1.5.2-Add-missing-limits-inclusion.patch b/dev-cpp/benchmark/files/benchmark-1.5.2-Add-missing-limits-inclusion.patch
new file mode 100644
index 00000000000..42bdbbef1f4
--- /dev/null
+++ b/dev-cpp/benchmark/files/benchmark-1.5.2-Add-missing-limits-inclusion.patch
@@ -0,0 +1,30 @@
+From 3d1c2677686718d906f28c1d4da001c42666e6d2 Mon Sep 17 00:00:00 2001
+From: Sergei Trofimovich <slyfox@inbox.ru>
+Date: Thu, 15 Oct 2020 09:12:40 +0100
+Subject: [PATCH] src/benchmark_register.h: add missing <limits> inclusion
+ (#1060)
+
+Noticed missing header when was building llvm with gcc-11:
+
+```
+llvm-project/llvm/utils/benchmark/src/benchmark_register.h:17:30:
+ error: 'numeric_limits' is not a member of 'std'
+ 17 | static const T kmax = std::numeric_limits<T>::max();
+ | ^~~~~~~~~~~~~~
+```
+---
+ src/benchmark_register.h | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/src/benchmark_register.h b/src/benchmark_register.h
+index 61377d74..204bf1d9 100644
+--- a/src/benchmark_register.h
++++ b/src/benchmark_register.h
+@@ -1,6 +1,7 @@
+ #ifndef BENCHMARK_REGISTER_H
+ #define BENCHMARK_REGISTER_H
+
++#include <limits>
+ #include <vector>
+
+ #include "check.h"
next reply other threads:[~2021-01-11 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 17:47 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-12 10:53 [gentoo-commits] repo/gentoo:master commit in: dev-cpp/benchmark/files/, dev-cpp/benchmark/ Marek Szuba
2021-08-13 16:31 Marek Szuba
2022-03-01 16:47 Marek Szuba
2024-03-21 2:41 Sam James
2024-08-28 6:39 Joonas Niilola
2025-03-05 11:26 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=1610387125.4add4f893cf2fb16b18d3c15bc9948a80802b66f.slyfox@gentoo \
--to=slyfox@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