From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/libcdaudio/
Date: Mon, 11 Mar 2024 14:24:09 +0000 (UTC) [thread overview]
Message-ID: <1710166970.5f7dd1f9e20c1b009c8031b1e5cee6f3b33022bb.sam@gentoo> (raw)
commit: 5f7dd1f9e20c1b009c8031b1e5cee6f3b33022bb
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Mon Mar 11 03:03:17 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Mar 11 14:22:50 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5f7dd1f9
media-libs/libcdaudio: mark as LTO-unsafe
Note: upstream is dead in terms of development, although apparently
still available to ask people on sourceforge if they are interested in
taking over maintenance.
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
media-libs/libcdaudio/libcdaudio-0.99.12-r5.ebuild | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/media-libs/libcdaudio/libcdaudio-0.99.12-r5.ebuild b/media-libs/libcdaudio/libcdaudio-0.99.12-r5.ebuild
index d64a5a9ac226..44b0a9468c60 100644
--- a/media-libs/libcdaudio/libcdaudio-0.99.12-r5.ebuild
+++ b/media-libs/libcdaudio/libcdaudio-0.99.12-r5.ebuild
@@ -3,7 +3,7 @@
EAPI=8
-inherit autotools
+inherit autotools flag-o-matic
DESCRIPTION="Library of cd audio related routines"
HOMEPAGE="https://libcdaudio.sourceforge.net/"
@@ -31,6 +31,15 @@ src_prepare() {
}
src_configure() {
+ # -Werror=lto-type-mismatch
+ #
+ # Upstream is pretty dead. The best that can be said is that as of a year
+ # ago if you posted support tickets, upstream would ask you:
+ #
+ # "libcdaudio is looking for a maintainer. Would you accept becoming a
+ # maintainer, so that you can integrate the change directly?"
+ filter-lto
+
econf --enable-threads --disable-static
}
next reply other threads:[~2024-03-11 14:24 UTC|newest]
Thread overview: 33+ 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-04-13 7:38 [gentoo-commits] repo/gentoo:master commit in: media-libs/libcdaudio/ Miroslav Šulc
2024-04-11 16:51 Arthur Zamarin
2024-04-11 10:32 Arthur Zamarin
2024-04-11 10:32 Arthur Zamarin
2024-04-11 9:58 Sam James
2024-04-11 9:00 Arthur Zamarin
2024-04-11 9:00 Arthur Zamarin
2024-03-11 14:24 Sam James
2024-03-11 14:24 Sam James
2024-03-11 14:24 Sam James
2023-07-07 7:31 Miroslav Šulc
2022-10-31 6:34 Miroslav Šulc
2022-10-25 10:44 Sam James
2022-10-25 9:49 Sam James
2022-10-23 19:36 Arthur Zamarin
2022-10-23 11:04 Sam James
2022-10-23 11:04 Sam James
2022-10-23 11:04 Sam James
2022-03-28 8:21 Miroslav Šulc
2022-03-28 6:53 Agostino Sarubbo
2022-03-28 6:51 Agostino Sarubbo
2022-03-26 19:45 Sam James
2022-03-26 19:11 Arthur Zamarin
2022-03-26 16:51 Arthur Zamarin
2022-03-26 16:49 Arthur Zamarin
2019-02-22 11:17 Mikle Kolyada
2019-02-22 11:15 Mikle Kolyada
2019-02-22 11:15 Mikle Kolyada
2019-02-12 21:03 Sergei Trofimovich
2019-02-12 8:12 Sergei Trofimovich
2019-02-12 8:11 Sergei Trofimovich
2019-02-11 7:13 Sergei Trofimovich
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=1710166970.5f7dd1f9e20c1b009c8031b1e5cee6f3b33022bb.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