From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-gfx/yafaray/files/, media-gfx/yafaray/
Date: Tue, 25 Apr 2023 21:30:25 +0000 (UTC) [thread overview]
Message-ID: <1682458030.31730190420eb7e3b472c4649b7f3c67cdb1dbc9.sam@gentoo> (raw)
commit: 31730190420eb7e3b472c4649b7f3c67cdb1dbc9
Author: Bernd Waibel <waebbl-gentoo <AT> posteo <DOT> net>
AuthorDate: Tue Apr 25 14:20:49 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Apr 25 21:27:10 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=31730190
media-gfx/yafaray: fix build with gcc-13
add missing #include statement
Bug: https://github.com/YafaRay/libYafaRay/issues/14
Closes: https://bugs.gentoo.org/895208
Signed-off-by: Bernd Waibel <waebbl-gentoo <AT> posteo.net>
Closes: https://github.com/gentoo/gentoo/pull/30748
Signed-off-by: Sam James <sam <AT> gentoo.org>
....1-add-missing-include-statements-for-gcc-13.patch | 19 +++++++++++++++++++
media-gfx/yafaray/metadata.xml | 3 +++
media-gfx/yafaray/yafaray-3.5.1-r4.ebuild | 1 +
3 files changed, 23 insertions(+)
diff --git a/media-gfx/yafaray/files/yafaray-3.5.1-add-missing-include-statements-for-gcc-13.patch b/media-gfx/yafaray/files/yafaray-3.5.1-add-missing-include-statements-for-gcc-13.patch
new file mode 100644
index 000000000000..066824f39c60
--- /dev/null
+++ b/media-gfx/yafaray/files/yafaray-3.5.1-add-missing-include-statements-for-gcc-13.patch
@@ -0,0 +1,19 @@
+From ca340cbfc518cc4b0655840453198620215535df Mon Sep 17 00:00:00 2001
+From: Bernd Waibel <waebbl-gentoo@posteo.net>
+Date: Tue, 25 Apr 2023 09:27:40 +0200
+Subject: [PATCH] add missing #include statements for gcc-13
+
+Signed-off-by: Bernd Waibel <waebbl-gentoo@posteo.net>
+--- a/include/core_api/session.h
++++ b/include/core_api/session.h
+@@ -25,6 +25,7 @@
+
+ #include <yafray_constants.h>
+ #include <utilities/threadUtils.h>
++#include <string>
+
+ __BEGIN_YAFRAY
+
+--
+2.40.0
+
diff --git a/media-gfx/yafaray/metadata.xml b/media-gfx/yafaray/metadata.xml
index b38bee5a6025..c509ab948629 100644
--- a/media-gfx/yafaray/metadata.xml
+++ b/media-gfx/yafaray/metadata.xml
@@ -28,4 +28,7 @@
Add support for <pkg>media-libs/opencv</pkg> image processing.
</flag>
</use>
+ <upstream>
+ <remote-id type="github">YafaRay/libYafaRay</remote-id>
+ </upstream>
</pkgmetadata>
diff --git a/media-gfx/yafaray/yafaray-3.5.1-r4.ebuild b/media-gfx/yafaray/yafaray-3.5.1-r4.ebuild
index 39fab8a3fae7..faee7f24fff4 100644
--- a/media-gfx/yafaray/yafaray-3.5.1-r4.ebuild
+++ b/media-gfx/yafaray/yafaray-3.5.1-r4.ebuild
@@ -47,6 +47,7 @@ BDEPEND="
PATCHES=(
"${FILESDIR}"/${P}-0001-respect-distribution-CFLAGS.patch
"${FILESDIR}"/${P}-add-missing-limits-header.patch
+ "${FILESDIR}"/${PN}-3.5.1-add-missing-include-statements-for-gcc-13.patch
)
DOCS=( AUTHORS.md CHANGELOG.md CODING.md INSTALL.md README.md )
next reply other threads:[~2023-04-25 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 21:30 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-13 7:31 [gentoo-commits] repo/gentoo:master commit in: media-gfx/yafaray/files/, media-gfx/yafaray/ Joonas Niilola
2020-04-26 13:37 Joonas Niilola
2018-05-29 21:43 Michał Górny
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=1682458030.31730190420eb7e3b472c4649b7f3c67cdb1dbc9.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