From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/nss/files/, dev-libs/nss/
Date: Wed, 1 Jun 2022 19:17:09 +0000 (UTC) [thread overview]
Message-ID: <1654111021.1309e3bab51ba812641509a623ab288235ea64f9.sam@gentoo> (raw)
commit: 1309e3bab51ba812641509a623ab288235ea64f9
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Jun 1 19:16:45 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Jun 1 19:17:01 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1309e3ba
dev-libs/nss: fix build with GCC 13
Closes: https://bugs.gentoo.org/849005
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-libs/nss/files/nss-3.79-gcc-13.patch | 33 ++++++++++++++++++++++++++++++++
dev-libs/nss/nss-3.79-r1.ebuild | 1 +
2 files changed, 34 insertions(+)
diff --git a/dev-libs/nss/files/nss-3.79-gcc-13.patch b/dev-libs/nss/files/nss-3.79-gcc-13.patch
new file mode 100644
index 000000000000..04bd977f3020
--- /dev/null
+++ b/dev-libs/nss/files/nss-3.79-gcc-13.patch
@@ -0,0 +1,33 @@
+https://github.com/nss-dev/nss/commit/edf5cb12af8a4668997b7edb65c7add4a1390b09
+https://bugs.gentoo.org/849005
+
+From: Sergei Trofimovich <slyich@gmail.com>
+Date: Thu, 26 May 2022 08:08:39 +0000
+Subject: [PATCH] Bug 1771273 - cpputil/databuffer.h: add missing <cstdint>
+ include r=nss-reviewers,mt
+
+Without the change build fails on this week's gcc-13 snapshot as:
+
+ ../../cpputil/databuffer.h:20:20: error: 'uint8_t' does not name a type
+ 20 | DataBuffer(const uint8_t* d, size_t l) : data_(nullptr), len_(0) {
+ | ^~~~~~~
+ ../../cpputil/databuffer.h:14:1: note: 'uint8_t' is defined in header '<cstdint>'; did you forget to '#include <cstdint>'?
+ 13 | #include <iostream>
+ +++ |+#include <cstdint>
+ 14 |
+
+Differential Revision: https://phabricator.services.mozilla.com/D147404
+
+--HG--
+extra : moz-landing-system : lando
+--- a/cpputil/databuffer.h
++++ b/cpputil/databuffer.h
+@@ -11,6 +11,7 @@
+ #include <cstring>
+ #include <iomanip>
+ #include <iostream>
++#include <cstdint>
+
+ namespace nss_test {
+
+
diff --git a/dev-libs/nss/nss-3.79-r1.ebuild b/dev-libs/nss/nss-3.79-r1.ebuild
index 0d91f55e8bd4..f0a86b80c6b6 100644
--- a/dev-libs/nss/nss-3.79-r1.ebuild
+++ b/dev-libs/nss/nss-3.79-r1.ebuild
@@ -40,6 +40,7 @@ PATCHES=(
"${FILESDIR}/${PN}-3.53-gentoo-fixups.patch"
"${FILESDIR}/${PN}-3.21-gentoo-fixup-warnings.patch"
"${FILESDIR}/${PN}-3.23-hppa-byte_order.patch"
+ "${FILESDIR}/${PN}-3.79-gcc-13.patch"
)
src_prepare() {
next reply other threads:[~2022-06-01 19:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 19:17 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-05 13:58 [gentoo-commits] repo/gentoo:master commit in: dev-libs/nss/files/, dev-libs/nss/ Joonas Niilola
2024-10-27 18:12 Joonas Niilola
2023-07-02 16:47 Joonas Niilola
2023-06-06 9:26 Sam James
2023-01-06 8:36 Joonas Niilola
2022-12-10 8:20 Joonas Niilola
2022-10-25 15:15 Joonas Niilola
2022-03-29 7:20 Joonas Niilola
2020-10-26 15:06 Thomas Deutschmann
2020-10-23 16:19 Thomas Deutschmann
2020-06-19 7:36 Lars Wendler
2020-03-31 17:50 Thomas Deutschmann
2018-06-06 16:12 Jory Pratt
2018-05-23 20:06 Ian Stakenvicius
2016-03-15 9:27 Lars Wendler
2015-12-25 15:39 Jeroen Roovers
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=1654111021.1309e3bab51ba812641509a623ab288235ea64f9.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