From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/libmodplug/
Date: Thu, 14 Mar 2024 06:06:17 +0000 (UTC) [thread overview]
Message-ID: <1710396331.99d9c29cd536fb1be71e277fd5a69b7dac3e1936.sam@gentoo> (raw)
commit: 99d9c29cd536fb1be71e277fd5a69b7dac3e1936
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Thu Mar 14 05:10:21 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Mar 14 06:05:31 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=99d9c29c
media-libs/libmodplug: mark as LTO-unsafe
There are 3 different upstreams described for this package. One
homepage, another SRC_URI, and a third in metadata.xml. Nowhere is this
actually maintained, however.
Closes: https://bugs.gentoo.org/921707
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
media-libs/libmodplug/libmodplug-0.8.9.1.ebuild | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/media-libs/libmodplug/libmodplug-0.8.9.1.ebuild b/media-libs/libmodplug/libmodplug-0.8.9.1.ebuild
index b92ffbcd510a..41ab576c6625 100644
--- a/media-libs/libmodplug/libmodplug-0.8.9.1.ebuild
+++ b/media-libs/libmodplug/libmodplug-0.8.9.1.ebuild
@@ -1,11 +1,11 @@
-# Copyright 1999-2023 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
MY_PVR="${PV}.r461"
-inherit autotools multilib-minimal
+inherit autotools flag-o-matic multilib-minimal
DESCRIPTION="Library for playing MOD-like music files"
HOMEPAGE="https://modplug-xmms.sourceforge.net/"
@@ -29,6 +29,13 @@ src_prepare() {
}
multilib_src_configure() {
+ # -Werror=odr
+ # https://bugs.gentoo.org/921707
+ #
+ # Upstream is dead for 2 years. Both of them -- the one in SRC_URI and the
+ # one in metadata.xml. Where to report a bug *to*, even? Answer: neither. :(
+ filter-lto
+
ECONF_SOURCE=${S} econf --disable-static
}
next reply other threads:[~2024-03-14 6:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 6:06 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-07 7:31 [gentoo-commits] repo/gentoo:master commit in: media-libs/libmodplug/ Miroslav Šulc
2023-04-05 14:27 Arthur Zamarin
2023-04-05 14:19 Arthur Zamarin
2023-04-05 14:12 Arthur Zamarin
2023-04-05 14:11 Arthur Zamarin
2023-04-05 14:11 Arthur Zamarin
2023-04-05 14:10 Arthur Zamarin
2023-04-05 12:01 Arthur Zamarin
2022-07-29 4:17 Sam James
2021-08-10 12:43 Marek Szuba
2021-05-31 20:45 David Seifert
2021-02-25 8:06 Andreas Sturmlechner
2021-02-24 23:53 Sam James
2021-02-24 23:49 Sam James
2021-02-24 23:25 Sam James
2021-02-24 23:07 Sam James
2021-02-19 17:55 Thomas Deutschmann
2021-02-01 15:07 Agostino Sarubbo
2021-01-29 20:50 Sam James
2020-07-17 21:29 Sergei Trofimovich
2018-10-05 5:48 Andreas Sturmlechner
2018-10-05 4:56 Markus Meier
2018-09-14 8:28 Tobias Klausmann
2018-09-07 23:03 Sergei Trofimovich
2018-09-07 22:54 Sergei Trofimovich
2018-09-07 22:43 Sergei Trofimovich
2018-09-07 14:28 Mikle Kolyada
2018-09-03 6:19 Sergei Trofimovich
2018-09-02 23:46 Thomas Deutschmann
2017-01-29 19:14 Fabian Groffen
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=1710396331.99d9c29cd536fb1be71e277fd5a69b7dac3e1936.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