From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-debug/valgrind/
Date: Sun, 26 May 2024 23:12:51 +0000 (UTC) [thread overview]
Message-ID: <1716765065.7dacecf376120d114419b41885bcfa01ed1d981e.sam@gentoo> (raw)
commit: 7dacecf376120d114419b41885bcfa01ed1d981e
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Sun May 26 22:17:49 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun May 26 23:11:05 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7dacecf3
dev-debug/valgrind: add whitelist for false positive configure implicit decls
The issue here is, yet again, that clang is a trash compiler and cannot
handle sensible diagnostic output. It warns you for implicit function
decls because it doesn't permit nested function definitions, *after* it
tells you that it doesn't permit the nested function. Instead of just
telling you that the former is forbidden.
Closes: https://bugs.gentoo.org/900396
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-debug/valgrind/valgrind-3.22.0-r2.ebuild | 7 +++++++
dev-debug/valgrind/valgrind-3.23.0.ebuild | 7 +++++++
dev-debug/valgrind/valgrind-9999.ebuild | 7 +++++++
3 files changed, 21 insertions(+)
diff --git a/dev-debug/valgrind/valgrind-3.22.0-r2.ebuild b/dev-debug/valgrind/valgrind-3.22.0-r2.ebuild
index b9204af91b7b..86ec190689c8 100644
--- a/dev-debug/valgrind/valgrind-3.22.0-r2.ebuild
+++ b/dev-debug/valgrind/valgrind-3.22.0-r2.ebuild
@@ -53,6 +53,13 @@ PATCHES=(
"${FILESDIR}"/0004-Bug-478624-Valgrind-incompatibility-with-binutils-2..patch
)
+QA_CONFIG_IMPL_DECL_SKIP+=(
+ # "checking if gcc accepts nested functions" but clang cannot handle good
+ # errors and reports both "function definition is not allowed here" and
+ # -Wimplicit-function-declaration. bug #900396
+ foo
+)
+
src_prepare() {
# Correct hard coded doc location
sed -i -e "s:doc/valgrind:doc/${PF}:" docs/Makefile.am || die
diff --git a/dev-debug/valgrind/valgrind-3.23.0.ebuild b/dev-debug/valgrind/valgrind-3.23.0.ebuild
index efcec418f726..48014039f07e 100644
--- a/dev-debug/valgrind/valgrind-3.23.0.ebuild
+++ b/dev-debug/valgrind/valgrind-3.23.0.ebuild
@@ -55,6 +55,13 @@ PATCHES=(
# From stable branch
)
+QA_CONFIG_IMPL_DECL_SKIP+=(
+ # "checking if gcc accepts nested functions" but clang cannot handle good
+ # errors and reports both "function definition is not allowed here" and
+ # -Wimplicit-function-declaration. bug #900396
+ foo
+)
+
src_prepare() {
# Correct hard coded doc location
sed -i -e "s:doc/valgrind:doc/${PF}:" docs/Makefile.am || die
diff --git a/dev-debug/valgrind/valgrind-9999.ebuild b/dev-debug/valgrind/valgrind-9999.ebuild
index efcec418f726..48014039f07e 100644
--- a/dev-debug/valgrind/valgrind-9999.ebuild
+++ b/dev-debug/valgrind/valgrind-9999.ebuild
@@ -55,6 +55,13 @@ PATCHES=(
# From stable branch
)
+QA_CONFIG_IMPL_DECL_SKIP+=(
+ # "checking if gcc accepts nested functions" but clang cannot handle good
+ # errors and reports both "function definition is not allowed here" and
+ # -Wimplicit-function-declaration. bug #900396
+ foo
+)
+
src_prepare() {
# Correct hard coded doc location
sed -i -e "s:doc/valgrind:doc/${PF}:" docs/Makefile.am || die
next reply other threads:[~2024-05-26 23:12 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-26 23:12 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-10 8:56 [gentoo-commits] repo/gentoo:master commit in: dev-debug/valgrind/ Sam James
2025-01-21 6:17 Arthur Zamarin
2025-01-21 6:17 Arthur Zamarin
2025-01-21 6:17 Arthur Zamarin
2024-12-01 9:00 Sam James
2024-11-27 6:24 Sam James
2024-11-03 21:26 Andreas K. Hüttel
2024-11-01 7:13 Sam James
2024-10-28 8:37 Sam James
2024-10-03 4:46 Sam James
2024-10-03 4:46 Sam James
2024-10-03 4:46 Sam James
2024-08-31 5:15 Sam James
2024-08-30 13:00 Jakov Smolić
2024-08-30 13:00 Jakov Smolić
2024-08-30 8:12 Sam James
2024-08-30 8:12 Sam James
2024-07-07 2:05 Sam James
2024-07-07 1:54 Sam James
2024-06-24 5:33 Sam James
2024-06-12 14:30 Sam James
2024-06-12 4:26 Sam James
2024-06-12 4:26 Sam James
2024-06-11 19:00 Sam James
2024-05-13 12:52 Arthur Zamarin
2024-05-13 1:06 Sam James
2024-05-13 1:06 Sam James
2024-05-13 1:06 Sam James
2024-04-26 21:35 Sam James
2024-04-26 19:36 Sam James
2024-04-25 8:55 Sam James
2024-04-25 8:55 Sam James
2024-04-24 23:03 Sam James
2024-04-20 4:23 Sam James
2024-01-14 4:32 Sam James
2024-01-14 4:19 Sam James
2024-01-14 4:14 Sam James
2024-01-14 4:08 Sam James
2024-01-14 3:17 Sam James
2024-01-14 3:17 Sam James
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=1716765065.7dacecf376120d114419b41885bcfa01ed1d981e.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