From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/harfbuzz/, media-libs/harfbuzz/files/
Date: Thu, 26 Jan 2023 07:23:54 +0000 (UTC) [thread overview]
Message-ID: <1674717493.57e3faad7b621b4c532b10ce11adf29a49154d1b.sam@gentoo> (raw)
commit: 57e3faad7b621b4c532b10ce11adf29a49154d1b
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 26 07:18:13 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jan 26 07:18:13 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=57e3faad
media-libs/harfbuzz: fix build w/ gcc 13
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../harfbuzz/files/harfbuzz-6.0.0-gcc-13.patch | 26 ++++++++++++++++++++++
media-libs/harfbuzz/harfbuzz-6.0.0.ebuild | 4 ++++
2 files changed, 30 insertions(+)
diff --git a/media-libs/harfbuzz/files/harfbuzz-6.0.0-gcc-13.patch b/media-libs/harfbuzz/files/harfbuzz-6.0.0-gcc-13.patch
new file mode 100644
index 000000000000..59536b173f21
--- /dev/null
+++ b/media-libs/harfbuzz/files/harfbuzz-6.0.0-gcc-13.patch
@@ -0,0 +1,26 @@
+https://github.com/harfbuzz/harfbuzz/commit/7dfa672dac958bdbc7703ab0920e167eaa126754
+
+From 7dfa672dac958bdbc7703ab0920e167eaa126754 Mon Sep 17 00:00:00 2001
+From: Sergei Trofimovich <slyich@gmail.com>
+Date: Mon, 16 Jan 2023 19:49:53 +0000
+Subject: [PATCH] test/threads/hb-subset-threads.cc: add missing <cstdio>
+ include
+
+This week's `gcc-13` snapshot cleaned further up it's standard headers
+and exposed missing declaration as a build failure:
+
+ ../test/threads/hb-subset-threads.cc: In function 'void test_operation(operation_t, const char*, const test_input_t&)':
+ ../test/threads/hb-subset-threads.cc:127:3: error: 'printf' was not declared in this scope
+
+ ../test/threads/hb-subset-threads.cc: In function 'int main(int, char**)':
+ ../test/threads/hb-subset-threads.cc:157:19: error: 'atoi' was not declared in this scope
+--- a/test/threads/hb-subset-threads.cc
++++ b/test/threads/hb-subset-threads.cc
+@@ -1,4 +1,6 @@
+ #include <cassert>
++#include <cstdio>
++#include <cstdlib>
+ #include <cstring>
+ #include <thread>
+ #include <condition_variable>
+
diff --git a/media-libs/harfbuzz/harfbuzz-6.0.0.ebuild b/media-libs/harfbuzz/harfbuzz-6.0.0.ebuild
index 6b4d0b8c3c11..9f5fab0d08ae 100644
--- a/media-libs/harfbuzz/harfbuzz-6.0.0.ebuild
+++ b/media-libs/harfbuzz/harfbuzz-6.0.0.ebuild
@@ -46,6 +46,10 @@ BDEPEND="
introspection? ( dev-util/glib-utils )
"
+PATCHES=(
+ "${FILESDIR}"/${P}-gcc-13.patch
+)
+
pkg_setup() {
python-any-r1_pkg_setup
if ! use debug ; then
next reply other threads:[~2023-01-26 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 7:23 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-04 13:29 [gentoo-commits] repo/gentoo:master commit in: media-libs/harfbuzz/, media-libs/harfbuzz/files/ Andreas Sturmlechner
2023-06-10 9:39 Andreas Sturmlechner
2023-04-30 17:16 Andreas Sturmlechner
2022-11-10 5:14 Sam James
2019-11-09 15:49 Sergei Trofimovich
2018-12-10 9:10 Lars Wendler
2018-05-03 11:06 Lars Wendler
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=1674717493.57e3faad7b621b4c532b10ce11adf29a49154d1b.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