From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/source-highlight/
Date: Thu, 28 Dec 2023 02:19:10 +0000 (UTC) [thread overview]
Message-ID: <1703729903.55795d1581fa3a3dff827600e61a0466f2c5913d.sam@gentoo> (raw)
commit: 55795d1581fa3a3dff827600e61a0466f2c5913d
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Thu Dec 28 01:34:49 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Dec 28 02:18:23 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=55795d15
dev-util/source-highlight: disallow building with LTO
It miscompiles with ODR violations. After elibtoolize, the build fails
with the recommended -Werror= flags for lto. Filter out -flto so that
users with global lto enabled don't miscompile source-highlight.
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-util/source-highlight/source-highlight-3.1.9-r2.ebuild | 2 ++
1 file changed, 2 insertions(+)
diff --git a/dev-util/source-highlight/source-highlight-3.1.9-r2.ebuild b/dev-util/source-highlight/source-highlight-3.1.9-r2.ebuild
index fb6cbdde1165..3a9b22fd5680 100644
--- a/dev-util/source-highlight/source-highlight-3.1.9-r2.ebuild
+++ b/dev-util/source-highlight/source-highlight-3.1.9-r2.ebuild
@@ -35,6 +35,8 @@ src_configure() {
# required as rev-dep of dev-libs/boost-1.62.0
# https://wiki.gentoo.org/wiki/Project:C%2B%2B/Maintaining_ABI
append-cxxflags -std=c++14
+ # ODR violations: https://savannah.gnu.org/bugs/index.php?65086
+ filter-lto
econf \
--with-boost="${EPREFIX}/usr" \
next reply other threads:[~2023-12-28 2:19 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 2:19 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-03 6:56 [gentoo-commits] repo/gentoo:master commit in: dev-util/source-highlight/ Sam James
2024-02-02 17:51 Arthur Zamarin
2024-02-02 14:46 Arthur Zamarin
2024-02-02 4:51 Sam James
2024-02-02 4:51 Sam James
2024-02-02 4:44 Sam James
2024-02-02 4:44 Sam James
2024-02-02 4:44 Sam James
2024-02-02 4:44 Sam James
2023-12-28 2:19 Sam James
2023-12-28 2:19 Sam James
2023-12-28 2:19 Sam James
2023-12-28 2:19 Sam James
2022-05-10 0:44 WANG Xuerui
2021-07-19 23:14 Marek Szuba
2021-01-06 22:55 Fabian Groffen
2020-07-25 9:18 Sergei Trofimovich
2020-07-18 18:09 Sam James
2020-06-28 20:44 Agostino Sarubbo
2020-06-28 20:37 Agostino Sarubbo
2020-06-28 20:33 Agostino Sarubbo
2020-06-28 20:30 Agostino Sarubbo
2020-06-25 7:00 Agostino Sarubbo
2020-06-24 17:22 Sergei Trofimovich
2020-06-22 18:23 Sergei Trofimovich
2020-03-23 23:58 Sergei Trofimovich
2019-11-29 23:12 Sergei Trofimovich
2019-11-29 23:03 Sergei Trofimovich
2019-11-29 20:50 Sergei Trofimovich
2019-11-29 20:37 Sergei Trofimovich
2019-11-18 2:18 Aaron Bauman
2019-04-17 20:01 Sergei Trofimovich
2019-04-13 13:57 Tiziano Müller
2019-04-09 9:48 Fabian Groffen
2018-05-13 10:44 Mart Raudsepp
2017-11-25 19:03 Sergei Trofimovich
2017-10-25 23:53 Manuel Rüger
2017-10-23 21:00 Sergei Trofimovich
2017-10-22 20:33 Thomas Deutschmann
2017-10-19 5:00 Markus Meier
2017-10-15 21:42 Sergei Trofimovich
2017-10-14 14:10 Sergei Trofimovich
2016-10-08 18:44 David Seifert
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=1703729903.55795d1581fa3a3dff827600e61a0466f2c5913d.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