From: "Eli Schwartz" <eschwartz@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-plugins/libvisual-plugins/
Date: Mon, 2 Sep 2024 01:27:08 +0000 (UTC) [thread overview]
Message-ID: <1725240390.792928fe00fad833e5da6c309b408549e2415ffe.eschwartz@gentoo> (raw)
commit: 792928fe00fad833e5da6c309b408549e2415ffe
Author: Eli Schwartz <eschwartz <AT> gentoo <DOT> org>
AuthorDate: Mon Sep 2 00:53:40 2024 +0000
Commit: Eli Schwartz <eschwartz <AT> gentoo <DOT> org>
CommitDate: Mon Sep 2 01:26:30 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=792928fe
media-plugins/libvisual-plugins: mark as LTO-unsafe, strict-aliasing unsafe
Closes: https://bugs.gentoo.org/927006
Signed-off-by: Eli Schwartz <eschwartz <AT> gentoo.org>
.../libvisual-plugins/libvisual-plugins-0.4.2-r1.ebuild | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/media-plugins/libvisual-plugins/libvisual-plugins-0.4.2-r1.ebuild b/media-plugins/libvisual-plugins/libvisual-plugins-0.4.2-r1.ebuild
index 88804a17d115..12b1861a1ec7 100644
--- a/media-plugins/libvisual-plugins/libvisual-plugins-0.4.2-r1.ebuild
+++ b/media-plugins/libvisual-plugins/libvisual-plugins-0.4.2-r1.ebuild
@@ -2,7 +2,7 @@
# Distributed under the terms of the GNU General Public License v2
EAPI=8
-inherit libtool multilib-minimal
+inherit flag-o-matic libtool multilib-minimal
DESCRIPTION="collection of visualization plugins for use with the libvisual framework"
HOMEPAGE="http://libvisual.org/"
@@ -42,6 +42,14 @@ src_prepare() {
}
multilib_src_configure() {
+ # -Werror=strict-aliasing
+ # https://bugs.gentoo.org/927006
+ # https://github.com/Libvisual/libvisual/issues/358
+ #
+ # Do not trust with LTO either.
+ append-flags -fno-strict-aliasing
+ filter-lto
+
ECONF_SOURCE=${S} \
econf \
$(use_enable jack) \
next reply other threads:[~2024-09-02 1:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 1:27 Eli Schwartz [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-11 18:37 [gentoo-commits] repo/gentoo:master commit in: media-plugins/libvisual-plugins/ Andreas Sturmlechner
2024-09-02 1:27 Eli Schwartz
2023-11-30 2:08 Sam James
2023-08-11 19:05 Arthur Zamarin
2023-08-04 23:15 Sam James
2023-08-03 15:10 Sam James
2023-07-26 7:22 Sam James
2023-07-26 7:11 Sam James
2023-06-25 23:06 Sebastian Pipping
2023-04-29 8:48 Sam James
2023-04-19 9:43 Sam James
2023-04-19 9:11 Arthur Zamarin
2023-04-19 8:00 Arthur Zamarin
2023-04-19 8:00 Arthur Zamarin
2023-04-19 8:00 Arthur Zamarin
2023-03-20 3:58 Sebastian Pipping
2023-01-22 19:04 Sam James
2023-01-22 19:04 Sam James
2023-01-22 17:52 Arthur Zamarin
2023-01-22 17:52 Arthur Zamarin
2023-01-22 17:52 Arthur Zamarin
2023-01-22 17:52 Arthur Zamarin
2022-12-06 0:17 Sebastian Pipping
2022-11-30 17:59 Sebastian Pipping
2022-11-30 17:57 Sebastian Pipping
2021-08-10 14:18 Marek Szuba
2020-09-23 10:53 Miroslav Šulc
2020-09-23 10:29 Agostino Sarubbo
2020-09-04 21:28 Sam James
2020-08-11 19:11 Sergei Trofimovich
2020-08-11 14:23 Agostino Sarubbo
2020-08-10 13:52 Agostino Sarubbo
2020-08-10 10:22 Agostino Sarubbo
2020-08-09 12:32 Sergei Trofimovich
2020-08-08 8:14 Miroslav Šulc
2020-07-31 11:04 Miroslav Šulc
2017-06-30 6:02 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=1725240390.792928fe00fad833e5da6c309b408549e2415ffe.eschwartz@gentoo \
--to=eschwartz@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