From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/watchman/files/
Date: Sun, 22 Jan 2023 06:04:36 +0000 (UTC) [thread overview]
Message-ID: <1674364231.c68adcf9c7e123e05e930b9da5d16ec27a3fa55b.sam@gentoo> (raw)
commit: c68adcf9c7e123e05e930b9da5d16ec27a3fa55b
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Jan 22 05:10:31 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Jan 22 05:10:31 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c68adcf9
dev-util/watchman: update patch to upstream variant
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-util/watchman/files/watchman-2023.01.16.00-gcc13.patch | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/dev-util/watchman/files/watchman-2023.01.16.00-gcc13.patch b/dev-util/watchman/files/watchman-2023.01.16.00-gcc13.patch
index 170450f43f69..20c70d29e28b 100644
--- a/dev-util/watchman/files/watchman-2023.01.16.00-gcc13.patch
+++ b/dev-util/watchman/files/watchman-2023.01.16.00-gcc13.patch
@@ -1,3 +1,16 @@
+https://github.com/facebook/watchman/pull/1089
+
+From 6535e011af5b89e9aa2a6faa60fc862f36f8b483 Mon Sep 17 00:00:00 2001
+From: Sam James <sam@gentoo.org>
+Date: Sun, 22 Jan 2023 05:09:25 +0000
+Subject: [PATCH] Fix build with GCC 13 (add missing <cstdint> include)
+
+GCC 13 (as usual for new compiler releases) shuffles around some
+internal includes and so <cstdint> is no longer transitively included.
+
+Explicitly include <cstdint> for uint32_t.
+
+Signed-off-by: Sam James <sam@gentoo.org>
--- a/watchman/Errors.h
+++ b/watchman/Errors.h
@@ -8,6 +8,7 @@
next reply other threads:[~2023-01-22 6:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 6:04 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-23 20:51 [gentoo-commits] repo/gentoo:master commit in: dev-util/watchman/files/ Alfredo Tupone
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=1674364231.c68adcf9c7e123e05e930b9da5d16ec27a3fa55b.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