From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/poke/
Date: Tue, 22 Nov 2022 08:11:29 +0000 (UTC) [thread overview]
Message-ID: <1669104514.d5b9075eac011e16538cc6689d470d875434d803.sam@gentoo> (raw)
commit: d5b9075eac011e16538cc6689d470d875434d803
Author: Arsen Arsenović <arsen <AT> aarsen <DOT> me>
AuthorDate: Mon Nov 21 10:05:29 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Nov 22 08:08:34 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d5b9075e
dev-util/poke: filter out LTO
On LTO'd systems, it was not possible to build poke due to an
autogenerated file producing code that lto-wrapper is unable to process.
We can just disable LTO in this case, until upstream gains support for
filtering out LTO flags for that single file.
Closes: https://bugs.gentoo.org/858461
Signed-off-by: Arsen Arsenović <arsen <AT> aarsen.me>
Closes: https://github.com/gentoo/gentoo/pull/28362
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-util/poke/poke-2.4.ebuild | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/dev-util/poke/poke-2.4.ebuild b/dev-util/poke/poke-2.4.ebuild
index 683291c3f9ba..88d5da88915a 100644
--- a/dev-util/poke/poke-2.4.ebuild
+++ b/dev-util/poke/poke-2.4.ebuild
@@ -3,6 +3,8 @@
EAPI=8
+inherit flag-o-matic
+
DESCRIPTION="Extensible editor for structured binary data"
HOMEPAGE="https://www.jemarch.net/poke"
SRC_URI="mirror://gnu/poke/${P}.tar.gz"
@@ -29,6 +31,13 @@ BDEPEND="sys-devel/flex
virtual/pkgconfig"
src_configure() {
+ # See bug 858461.
+ # Upstream support might happen one day. For context, only one file needs
+ # LTO to be disabled (since it's an autogenerated bytecode interpreter),
+ # others do not. The build system will handle this at some point in the
+ # future. Until then, just filter out LTO.
+ filter-lto
+
# NB --disable-{gui,mi}:
# These (AFAICT) have no consumers in Gentoo, and should not get any,
# preferably. They are slated for removal with Poke 3 (should happen
next reply other threads:[~2022-11-22 8:11 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 8:11 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-14 14:42 [gentoo-commits] repo/gentoo:master commit in: dev-util/poke/ Arthur Zamarin
2024-06-14 13:36 Arsen Arsenović
2024-04-02 11:55 Arsen Arsenović
2024-04-02 11:55 Arsen Arsenović
2024-02-11 13:23 Arsen Arsenović
2024-01-22 14:04 Arsen Arsenović
2024-01-20 15:56 Arsen Arsenović
2023-11-23 19:53 Sam James
2023-11-21 19:37 Arsen Arsenović
2023-08-20 16:31 Arsen Arsenović
2023-05-14 16:42 Arsen Arsenović
2023-05-14 9:32 Arsen Arsenović
2023-04-18 0:22 Arsen Arsenović
2023-04-01 16:30 Arthur Zamarin
2023-01-25 21:10 Arsen Arsenović
2023-01-25 0:29 Arsen Arsenović
2023-01-25 0:29 Arsen Arsenović
2023-01-24 23:46 Arsen Arsenović
2023-01-24 23:46 Arsen Arsenović
2023-01-24 23:46 Arsen Arsenović
2023-01-21 18:00 Arsen Arsenović
2023-01-21 18:00 Arsen Arsenović
2022-12-05 19:00 Arthur Zamarin
2022-12-04 21:15 Sam James
2022-12-03 11:06 Sam James
2022-09-17 14:34 Sam James
2022-09-17 14:34 Sam James
2022-04-17 19:00 Sam James
2022-04-10 15:12 Florian Schmaus
2022-04-10 15:12 Florian Schmaus
2022-04-10 15:12 Florian Schmaus
2022-02-23 4:05 Sam James
2022-02-23 4:05 Sam James
2021-07-30 8:55 Sergei Trofimovich
2021-06-12 10:07 Sergei Trofimovich
2021-06-06 9:20 Sergei Trofimovich
2021-04-24 12:37 Sergei Trofimovich
2021-04-19 23:41 Sergei Trofimovich
2021-04-02 9:54 Sergei Trofimovich
2021-03-27 22:18 Sergei Trofimovich
2021-03-25 20:31 Sergei Trofimovich
2021-02-26 22:38 Sergei Trofimovich
2021-02-26 22:01 Sergei Trofimovich
2021-02-26 19:59 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=1669104514.d5b9075eac011e16538cc6689d470d875434d803.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