From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/kyua/
Date: Tue, 14 Jan 2025 14:58:08 +0000 (UTC) [thread overview]
Message-ID: <1736866667.9e089b30a9eb24208fc37ef1e561b0f9031c131d.sam@gentoo> (raw)
commit: 9e089b30a9eb24208fc37ef1e561b0f9031c131d
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Jan 14 14:57:08 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jan 14 14:57:47 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9e089b30
dev-util/kyua: filter LTO for now
I don't yet understand what's going wrong so filter LTO until investigated;
bisected it to a build system change and it feels like some macro is/isn't
being set consistently now (we've had that before) which causes -Wodr
warnings.
Bug: https://bugs.gentoo.org/948053
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-util/kyua/kyua-0.14.ebuild | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/dev-util/kyua/kyua-0.14.ebuild b/dev-util/kyua/kyua-0.14.ebuild
index feca4c10e157..6a1d218752d9 100644
--- a/dev-util/kyua/kyua-0.14.ebuild
+++ b/dev-util/kyua/kyua-0.14.ebuild
@@ -3,7 +3,7 @@
EAPI=8
-inherit autotools
+inherit autotools flag-o-matic
DESCRIPTION="Testing framework for infrastructure software"
HOMEPAGE="https://github.com/freebsd/kyua"
@@ -32,6 +32,9 @@ src_prepare() {
}
src_configure() {
+ # bug #948053
+ filter-lto
+
# Skip coredump tests; they fail when sudo sets RLIMIT_CORE = 0.
cat >"${T}/kyua.conf" <<-EOF || die
syntax(2)
next reply other threads:[~2025-01-14 14:58 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 14:58 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-12 5:14 [gentoo-commits] repo/gentoo:master commit in: dev-util/kyua/ Mike Gilbert
2024-05-25 16:59 Mike Gilbert
2024-05-25 16:58 Mike Gilbert
2024-05-25 16:58 Mike Gilbert
2024-05-24 20:10 Mike Gilbert
2024-05-21 21:17 Mike Gilbert
2024-04-24 18:13 Arthur Zamarin
2024-04-24 17:59 Arthur Zamarin
2024-04-24 17:43 Arthur Zamarin
2024-04-24 17:18 Arthur Zamarin
2024-04-24 17:17 Arthur Zamarin
2024-04-24 17:14 Arthur Zamarin
2024-04-24 17:14 Arthur Zamarin
2023-07-26 6:35 Sam James
2023-07-26 6:32 Sam James
2021-07-28 11:28 Marek Szuba
2020-11-28 10:13 Sam James
2019-02-16 13:37 Mikle Kolyada
2019-02-16 13:37 Mikle Kolyada
2019-01-17 13:13 Mart Raudsepp
2018-10-17 16:48 Mikle Kolyada
2018-09-07 17:18 Mike Gilbert
2018-09-06 21:14 Mike Gilbert
2017-12-05 6:47 Matt Turner
2017-11-06 11:46 Manuel RĂ¼ger
2017-11-02 14:33 Tobias Klausmann
2017-09-30 17:14 Matt Turner
2017-09-30 17:14 Matt Turner
2017-09-12 8:00 Sergei Trofimovich
2017-09-11 16:56 Mike Gilbert
2017-09-11 8:10 Sergei Trofimovich
2017-08-10 4:41 Markus Meier
2017-08-09 21:05 Sergei Trofimovich
2017-08-05 14:25 Sergei Trofimovich
2017-07-04 18:28 Mike Gilbert
2017-06-18 20:56 Sergei Trofimovich
2017-05-14 10:55 Markus Meier
2017-05-13 6:26 Markus Meier
2017-05-09 12:40 Jeroen Roovers
2017-05-09 7:49 Tobias Klausmann
2017-05-08 16:08 Mike Gilbert
2017-05-07 18:39 Mike Gilbert
2017-05-07 18:39 Mike Gilbert
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=1736866667.9e089b30a9eb24208fc37ef1e561b0f9031c131d.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