From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-debug/valgrind/
Date: Wed, 24 Apr 2024 23:03:13 +0000 (UTC) [thread overview]
Message-ID: <1713999779.64b018a2c40307b048017ee4b9e9afafe1ffb19e.sam@gentoo> (raw)
commit: 64b018a2c40307b048017ee4b9e9afafe1ffb19e
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Apr 24 23:02:34 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Apr 24 23:02:59 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=64b018a2
dev-debug/valgrind: add upstream bug link for -fno-sa in tests, sync live
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-debug/valgrind/valgrind-3.23.0_rc1.ebuild | 1 +
dev-debug/valgrind/valgrind-9999.ebuild | 3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/dev-debug/valgrind/valgrind-3.23.0_rc1.ebuild b/dev-debug/valgrind/valgrind-3.23.0_rc1.ebuild
index 625625cc2679..312c4f8b724e 100644
--- a/dev-debug/valgrind/valgrind-3.23.0_rc1.ebuild
+++ b/dev-debug/valgrind/valgrind-3.23.0_rc1.ebuild
@@ -115,6 +115,7 @@ src_configure() {
src_test() {
# fxsave.o, tronical.o have textrels
+ # -fno-strict-aliasing: https://bugs.kde.org/show_bug.cgi?id=486093
emake CFLAGS="${CFLAGS} -fno-strict-aliasing" LDFLAGS="${LDFLAGS} -Wl,-z,notext" check
}
diff --git a/dev-debug/valgrind/valgrind-9999.ebuild b/dev-debug/valgrind/valgrind-9999.ebuild
index e79b850d13a3..312c4f8b724e 100644
--- a/dev-debug/valgrind/valgrind-9999.ebuild
+++ b/dev-debug/valgrind/valgrind-9999.ebuild
@@ -115,7 +115,8 @@ src_configure() {
src_test() {
# fxsave.o, tronical.o have textrels
- emake LDFLAGS="${LDFLAGS} -Wl,-z,notext" check
+ # -fno-strict-aliasing: https://bugs.kde.org/show_bug.cgi?id=486093
+ emake CFLAGS="${CFLAGS} -fno-strict-aliasing" LDFLAGS="${LDFLAGS} -Wl,-z,notext" check
}
src_install() {
next reply other threads:[~2024-04-24 23:03 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 23:03 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-31 22:23 [gentoo-commits] repo/gentoo:master commit in: dev-debug/valgrind/ Sam James
2025-03-28 18:22 Sam James
2025-03-28 18:22 Sam James
2025-03-28 18:22 Sam James
2025-03-28 18:22 Sam James
2025-02-10 8:56 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-26 23:12 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-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=1713999779.64b018a2c40307b048017ee4b9e9afafe1ffb19e.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