From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libowfat/
Date: Sun, 17 Mar 2024 05:34:55 +0000 (UTC) [thread overview]
Message-ID: <1710653321.c4a75bbddb54b323e799eb95d9d0488986eb0f51.sam@gentoo> (raw)
commit: c4a75bbddb54b323e799eb95d9d0488986eb0f51
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Sun Mar 17 04:02:35 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Mar 17 05:28:41 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c4a75bbd
dev-libs/libowfat: mark as LTO-unsafe
It breaks consumers, largely because... it is a static library. Frankly,
static libraries shouldn't be LTO'ed at all. We definitely cannot
cross-LTO between libowfat and e.g. gatling anyway.
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-libs/libowfat/libowfat-0.32-r5.ebuild | 8 +++++++-
dev-libs/libowfat/libowfat-0.33-r1.ebuild | 8 +++++++-
2 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/dev-libs/libowfat/libowfat-0.32-r5.ebuild b/dev-libs/libowfat/libowfat-0.32-r5.ebuild
index da8af4daacc6..45ea340b25da 100644
--- a/dev-libs/libowfat/libowfat-0.32-r5.ebuild
+++ b/dev-libs/libowfat/libowfat-0.32-r5.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI="8"
@@ -38,6 +38,12 @@ src_prepare() {
}
src_compile() {
+ # Primary use case is for code by the same author. Which then fails with
+ # LTO errors. It builds a static library only, anyway. Result: LTO can be
+ # used if you don't upgrade the compiler. If you do, the compiler errors,
+ # or if you are unlucky, ICEs. Just don't use LTO, there is no point...
+ filter-lto
+
emake \
CC="$(tc-getCC)" \
AR="$(tc-getAR)" \
diff --git a/dev-libs/libowfat/libowfat-0.33-r1.ebuild b/dev-libs/libowfat/libowfat-0.33-r1.ebuild
index 140aed4ff868..456716706290 100644
--- a/dev-libs/libowfat/libowfat-0.33-r1.ebuild
+++ b/dev-libs/libowfat/libowfat-0.33-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI="8"
@@ -23,6 +23,12 @@ pkg_setup() {
}
src_compile() {
+ # Primary use case is for code by the same author. Which then fails with
+ # LTO errors. It builds a static library only, anyway. Result: LTO can be
+ # used if you don't upgrade the compiler. If you do, the compiler errors,
+ # or if you are unlucky, ICEs. Just don't use LTO, there is no point...
+ filter-lto
+
# workaround for broken dependencies
emake headers
next reply other threads:[~2024-03-17 5:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 5:34 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-07 13:52 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libowfat/ David Seifert
2022-03-20 0:53 Sam James
2022-02-14 8:01 Agostino Sarubbo
2022-02-13 22:15 Jakov Smolić
2022-02-13 14:58 Sam James
2021-11-17 21:56 Sam James
2021-08-16 1:58 Sam James
2021-08-16 1:58 Sam James
2021-08-16 1:58 Sam James
2021-08-16 1:58 Sam James
2021-05-31 20:45 David Seifert
2019-05-26 11:49 Mikle Kolyada
2019-05-20 17:50 Sergei Trofimovich
2019-05-19 15:48 Thomas Deutschmann
2019-04-10 22:03 Sergei Trofimovich
2018-12-03 21:55 Sergei Trofimovich
2018-12-01 18:46 Thomas Deutschmann
2018-11-28 2:07 Thomas Deutschmann
2018-11-11 13:07 Pacho Ramos
2017-12-20 21:03 Thomas Deutschmann
2017-12-16 17:24 Tobias Klausmann
2017-12-08 21:58 Thomas Deutschmann
2017-12-04 22:07 Sergei Trofimovich
2017-12-04 8:01 Sergei Trofimovich
2017-11-29 23:19 Andreas Sturmlechner
2017-11-29 23:19 Andreas Sturmlechner
2017-11-29 23:19 Andreas Sturmlechner
2016-10-20 17:30 Patrick Lauer
2016-01-19 21:48 Jeroen Roovers
2016-01-19 9:28 Patrick Lauer
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=1710653321.c4a75bbddb54b323e799eb95d9d0488986eb0f51.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