public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/libfpx/
Date: Wed, 13 Mar 2024 21:04:41 +0000 (UTC)	[thread overview]
Message-ID: <1710363848.1ebd8326257a79006c4517d93f3a07eadd000834.sam@gentoo> (raw)

commit:     1ebd8326257a79006c4517d93f3a07eadd000834
Author:     Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Wed Mar 13 19:26:45 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Mar 13 21:04:08 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1ebd8326

media-libs/libfpx: mark as LTO-unsafe, strict-aliasing unsafe

Closes: https://bugs.gentoo.org/859913
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>

 media-libs/libfpx/libfpx-1.3.1_p10.ebuild | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/media-libs/libfpx/libfpx-1.3.1_p10.ebuild b/media-libs/libfpx/libfpx-1.3.1_p10.ebuild
index d1090723cb3e..782c66231228 100644
--- a/media-libs/libfpx/libfpx-1.3.1_p10.ebuild
+++ b/media-libs/libfpx/libfpx-1.3.1_p10.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
@@ -30,6 +30,14 @@ src_prepare() {
 }
 
 src_configure() {
+	# -Werror=strict-aliasing
+	# https://bugs.gentoo.org/859913
+	# https://github.com/ImageMagick/libfpx/issues/6
+	#
+	# Do not trust for LTO either
+	append-flags -fno-strict-aliasing
+	filter-lto
+
 	append-ldflags -Wl,--no-undefined
 	econf \
 		$(use_enable static-libs static) \


             reply	other threads:[~2024-03-13 21:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13 21:04 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-10  2:45 [gentoo-commits] repo/gentoo:master commit in: media-libs/libfpx/ Sam James
2024-05-23 19:29 Arthur Zamarin
2024-05-23 19:28 Arthur Zamarin
2024-04-19 11:43 Sam James
2024-04-19 10:46 Sam James
2024-04-19 10:46 Sam James
2024-04-19 10:43 Sam James
2024-04-19 10:43 Sam James
2024-04-19 10:43 Sam James
2024-04-19 10:38 Sam James
2024-04-19  9:38 Arthur Zamarin
2024-03-16 12:13 Conrad Kostecki
2022-05-17 13:07 WANG Xuerui
2022-02-13 21:08 Conrad Kostecki
2021-06-25  1:33 Yixun Lan
2019-05-08 22:56 Andreas Sturmlechner
2019-05-08 22:56 Andreas Sturmlechner
2019-04-14 14:37 Aaron Bauman
2018-06-21 19:21 Sergei Trofimovich
2017-10-24 17:38 Markus Meier
2017-10-16 19:50 Sergei Trofimovich
2017-10-16  8:28 Sergei Trofimovich
2017-10-16  8:28 Sergei Trofimovich
2017-10-15 22:21 Manuel Rüger
2017-10-13 15:01 Thomas Deutschmann
2017-10-13  9:09 Sergei Trofimovich
2017-10-12 21:19 Thomas Deutschmann
2017-06-18  9:51 Alexis Ballier
2017-01-29 19:14 Fabian Groffen
2016-04-06 19:48 Markus Meier
2016-03-20 11:53 Agostino Sarubbo
2016-03-15 16:39 Agostino Sarubbo
2016-03-14 18:35 Tobias Klausmann
2016-03-11 16:37 Markus Meier
2016-03-02 13:58 Agostino Sarubbo
2016-02-22  6:01 Jeroen Roovers
2016-02-20 11:24 Jeroen Roovers

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=1710363848.1ebd8326257a79006c4517d93f3a07eadd000834.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