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: x11-drivers/xf86-video-openchrome/
Date: Mon, 11 Mar 2024 14:24:08 +0000 (UTC)	[thread overview]
Message-ID: <1710166961.e9ba22b61ce631b1f9ebf19c74ec04eef55dc509.sam@gentoo> (raw)

commit:     e9ba22b61ce631b1f9ebf19c74ec04eef55dc509
Author:     Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Sun Mar 10 19:53:24 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Mar 11 14:22:41 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e9ba22b6

x11-drivers/xf86-video-openchrome: mark LTO-unsafe, strict-aliasing unsafe

Freedesktop moved to gitlab and dropped support for previous project
hosting methods to read-only. It appears openchrome never made the
migration. May be dead -- it hasn't been developed in some time, the
cgit HEAD is 4 years old and a non-default branch is "only" a year old.

Not really sure where to report a bug to. ;)

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

 .../xf86-video-openchrome-0.6.0.ebuild                     | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)

diff --git a/x11-drivers/xf86-video-openchrome/xf86-video-openchrome-0.6.0.ebuild b/x11-drivers/xf86-video-openchrome/xf86-video-openchrome-0.6.0.ebuild
index 1219380c354b..05f4f4c71a97 100644
--- a/x11-drivers/xf86-video-openchrome/xf86-video-openchrome-0.6.0.ebuild
+++ b/x11-drivers/xf86-video-openchrome/xf86-video-openchrome-0.6.0.ebuild
@@ -1,10 +1,10 @@
-# Copyright 1999-2021 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=7
 
 XORG_DRI="always"
-inherit xorg-3
+inherit flag-o-matic xorg-3
 
 DESCRIPTION="X.Org driver for VIA/S3G cards"
 HOMEPAGE="https://www.freedesktop.org/wiki/Openchrome/"
@@ -26,6 +26,16 @@ DEPEND="
 PATCHES=( "${FILESDIR}"/${P}-fno-common.patch )
 
 src_configure() {
+	# -Werror=strict-aliasing
+	# https://bugs.gentoo.org/864406
+	# Upstream appears to have never migrated from the old bugzilla and
+	# cgit hosting over to gitlab.fd.o, no activity in a year, no way
+	# to report a bug I guess. Yay dead software.
+	#
+	# Do not trust for LTO either
+	append-flags -fno-strict-aliasing
+	filter-lto
+
 	local XORG_CONFIGURE_OPTIONS=(
 		$(use_enable debug)
 		$(use_enable debug xv-debug)


             reply	other threads:[~2024-03-11 14:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 14:24 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-06 18:42 [gentoo-commits] repo/gentoo:master commit in: x11-drivers/xf86-video-openchrome/ Matt Turner
2021-03-19 22:40 David Seifert
2019-01-20  6:52 Matt Turner
2019-01-20  5:43 Matt Turner
2017-06-01  9:13 Agostino Sarubbo
2017-05-31 13:06 Agostino Sarubbo
2017-03-08  1:37 Matt Turner
2016-09-17 11:14 Pacho Ramos
2016-09-17 10:49 Pacho Ramos
2016-07-06 23:12 Chí-Thanh Christopher Nguyễn
2016-05-29 18:55 Chí-Thanh Christopher Nguyễn

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=1710166961.e9ba22b61ce631b1f9ebf19c74ec04eef55dc509.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