From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-electronics/geda/
Date: Thu, 21 Mar 2024 05:58:46 +0000 (UTC) [thread overview]
Message-ID: <1711000661.12bd3b6d3f2239776739e854f01b4dbc02f3c91b.sam@gentoo> (raw)
commit: 12bd3b6d3f2239776739e854f01b4dbc02f3c91b
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Thu Mar 21 05:28:39 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Mar 21 05:57:41 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=12bd3b6d
sci-electronics/geda: avoid fatal warning for maybe-uninitialized
LTO makes the compiler better able to spot this. But it isn't something
the entire build should fail due to, not for stable release tags of
existing software.
Closes: https://bugs.gentoo.org/862453
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
sci-electronics/geda/geda-1.10.2-r2.ebuild | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/sci-electronics/geda/geda-1.10.2-r2.ebuild b/sci-electronics/geda/geda-1.10.2-r2.ebuild
index 4d2d3cab6699..7983738c270b 100644
--- a/sci-electronics/geda/geda-1.10.2-r2.ebuild
+++ b/sci-electronics/geda/geda-1.10.2-r2.ebuild
@@ -62,6 +62,10 @@ src_prepare() {
rm docs/wiki/media/geda/pcb_plugin_template.tar.gz || die
rm docs/wiki/media/pcb/plugin_debug_window.tar.gz || die
+ # -Wmaybe-uninitialized is made fatal, which is not ideal for building
+ # releases. Upstream is working on fixing these anyway.
+ sed -i '/Werror_maybe_uninitialized_IF_SUPPORTED/d' configure.ac
+
eautoreconf
}
next reply other threads:[~2024-03-21 5:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 5:58 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-09 22:37 [gentoo-commits] repo/gentoo:master commit in: sci-electronics/geda/ Andreas K. Hüttel
2024-11-09 22:37 Andreas K. Hüttel
2024-11-08 3:54 Sam James
2024-03-21 6:00 Sam James
2024-03-21 5:58 Sam James
2024-03-21 5:58 Sam James
2024-03-12 6:45 Sam James
2023-12-16 1:29 Sam James
2022-03-03 10:20 Andrew Ammerlaan
2022-03-03 9:48 Andrew Ammerlaan
2022-03-02 16:41 Andrew Ammerlaan
2022-03-02 12:35 Andrew Ammerlaan
2021-11-18 23:50 Georgy Yakovlev
2019-05-20 16:17 Thomas Beierlein
2019-05-20 16:17 Thomas Beierlein
2018-08-05 20:50 Mikle Kolyada
2018-08-05 1:03 Thomas Deutschmann
2018-06-16 9:08 Thomas Beierlein
2017-12-11 8:20 Michael Weber
2017-01-29 19:16 Michael Weber
2017-01-29 16:45 Michael Weber
2017-01-29 16:45 Michael Weber
2016-08-11 23:35 Denis Dupeyron
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=1711000661.12bd3b6d3f2239776739e854f01b4dbc02f3c91b.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