From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-sound/din/, media-sound/din/files/
Date: Mon, 14 Jun 2021 16:11:34 +0000 (UTC) [thread overview]
Message-ID: <1623687081.238d4c26092568ac7c3bb25753405909d61d8c8c.sam@gentoo> (raw)
commit: 238d4c26092568ac7c3bb25753405909d61d8c8c
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Jun 14 15:15:55 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Jun 14 16:11:21 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=238d4c26
media-sound/din: fix build with GCC 11
Closes: https://bugs.gentoo.org/787185
Signed-off-by: Sam James <sam <AT> gentoo.org>
media-sound/din/din-50.2.ebuild | 1 +
.../files/din-50.2-gcc11-rename-identifier.patch | 41 ++++++++++++++++++++++
2 files changed, 42 insertions(+)
diff --git a/media-sound/din/din-50.2.ebuild b/media-sound/din/din-50.2.ebuild
index 4d68ab765af..38869408d19 100644
--- a/media-sound/din/din-50.2.ebuild
+++ b/media-sound/din/din-50.2.ebuild
@@ -35,6 +35,7 @@ REQUIRED_USE="|| ( alsa jack )"
PATCHES=(
"${FILESDIR}/${PN}-49.1-makefile.patch"
"${FILESDIR}/${PN}-48-fix-random-constants.patch"
+ "${FILESDIR}/${PN}-50.2-gcc11-rename-identifier.patch"
)
src_prepare() {
diff --git a/media-sound/din/files/din-50.2-gcc11-rename-identifier.patch b/media-sound/din/files/din-50.2-gcc11-rename-identifier.patch
new file mode 100644
index 00000000000..4d65f65b038
--- /dev/null
+++ b/media-sound/din/files/din-50.2-gcc11-rename-identifier.patch
@@ -0,0 +1,41 @@
+https://bugs.gentoo.org/787185
+
+From 9ea918cfdfcd99fbcac64a820ddbaefb562c11a0 Mon Sep 17 00:00:00 2001
+From: Sam James <sam@gentoo.org>
+Date: Mon, 14 Jun 2021 15:06:58 +0000
+Subject: [PATCH] src/help.h: Rename __help identifier
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+__help is reserved, so we need to rename it to fix a build failure with GCC 11:
+
+ "In addition to the names documented in this manual, reserved names include all
+ external identifiers (global functions and variables) that begin with an
+ underscore (‘_’) and all identifiers regardless of use that begin with either
+ two underscores or an underscore followed by a capital letter are reserved names."
+ -- glibc manual, 1.3.3 Reserved Names
+
+Signed-off-by: Sam James <sam@gentoo.org>
+---
+ src/help.h | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/src/help.h b/src/help.h
+index ae0954b..af7f178 100644
+--- a/src/help.h
++++ b/src/help.h
+@@ -5,8 +5,8 @@
+ * For more information, please visit https://dinisnoise.org/
+ */
+
+-#ifndef __help
+-#define __help
++#ifndef DIN_help
++#define DIN_help
+ #include <string>
+ #include <vector>
+ struct help {
+--
+2.32.0
+
next reply other threads:[~2021-06-14 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 16:11 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-16 12:47 [gentoo-commits] repo/gentoo:master commit in: media-sound/din/, media-sound/din/files/ Miroslav Šulc
2024-01-14 12:11 Miroslav Šulc
2022-10-09 8:04 Miroslav Šulc
2022-01-13 9:29 Miroslav Šulc
2021-12-11 18:18 Miroslav Šulc
2021-09-26 6:07 Miroslav Šulc
2020-12-22 13:20 Miroslav Šulc
2017-06-30 5:34 Alexis Ballier
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=1623687081.238d4c26092568ac7c3bb25753405909d61d8c8c.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