From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/shiboken6/
Date: Wed, 28 Feb 2024 22:57:16 +0000 (UTC) [thread overview]
Message-ID: <1709161021.d76a2cff990028e249d92d195f002174df3f58d3.sam@gentoo> (raw)
commit: d76a2cff990028e249d92d195f002174df3f58d3
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Wed Feb 28 21:48:25 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Feb 28 22:57:01 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d76a2cff
dev-python/shiboken6: mark as LTO-unsafe
Closes: https://bugs.gentoo.org/925479
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/shiboken6/shiboken6-6.6.2.ebuild | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/dev-python/shiboken6/shiboken6-6.6.2.ebuild b/dev-python/shiboken6/shiboken6-6.6.2.ebuild
index 428293079631..4187835e2818 100644
--- a/dev-python/shiboken6/shiboken6-6.6.2.ebuild
+++ b/dev-python/shiboken6/shiboken6-6.6.2.ebuild
@@ -16,7 +16,7 @@ PYTHON_COMPAT=( python3_{10..12} )
LLVM_COMPAT=( {15..17} )
-inherit cmake llvm-r1 python-r1 toolchain-funcs
+inherit cmake flag-o-matic llvm-r1 python-r1 toolchain-funcs
MY_PN="pyside-setup-everywhere-src"
@@ -109,6 +109,11 @@ src_prepare() {
}
src_configure() {
+ # -Werror=odr
+ # https://bugs.gentoo.org/925479
+ # https://bugreports.qt.io/browse/PYSIDE-2619
+ filter-lto
+
# Minimal tests for now, 2 failing with the extended version
# FIXME Subscripted generics cannot be used with class and instance checks
local mycmakeargs=(
next reply other threads:[~2024-02-28 22:57 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 22:57 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-19 20:08 [gentoo-commits] repo/gentoo:master commit in: dev-python/shiboken6/ Ionen Wolkens
2025-02-19 17:00 Nowa Ammerlaan
2025-02-19 9:10 Nowa Ammerlaan
2025-02-19 9:08 Nowa Ammerlaan
2025-01-25 12:25 Arthur Zamarin
2025-01-25 10:41 Sam James
2025-01-06 21:47 Sam James
2025-01-06 7:08 WANG Xuerui
2024-12-26 13:19 Nowa Ammerlaan
2024-12-20 16:09 Nowa Ammerlaan
2024-09-29 15:02 Andrew Ammerlaan
2024-07-28 17:39 Arthur Zamarin
2024-07-23 3:40 Eli Schwartz
2024-07-10 4:21 Ionen Wolkens
2024-06-25 16:50 Jakov Smolić
2024-06-19 16:38 Andrew Ammerlaan
2024-06-02 1:46 Sam James
2024-06-02 0:14 Sam James
2024-05-21 16:00 Andrew Ammerlaan
2024-04-17 22:01 Sam James
2024-04-12 15:32 Andrew Ammerlaan
2024-03-03 4:00 Sam James
2024-02-16 8:58 Andrew Ammerlaan
2024-02-11 14:38 Andrew Ammerlaan
2023-12-07 18:44 Andrew Ammerlaan
2023-10-18 8:54 Andrew Ammerlaan
2023-10-09 10:41 Andrew Ammerlaan
2023-10-06 7:43 Andrew Ammerlaan
2023-10-03 15:27 Andrew Ammerlaan
2023-10-03 14:27 Andrew Ammerlaan
2023-08-17 7:49 Andrew Ammerlaan
2023-07-24 11:34 Michał Górny
2023-06-14 19:59 Andrew Ammerlaan
2023-06-11 14:16 Andrew Ammerlaan
2023-04-19 16:54 Andrew Ammerlaan
2023-04-08 6:08 Michał Górny
2023-04-01 14:51 Andrew Ammerlaan
2023-01-12 15:13 Andrew Ammerlaan
2022-11-07 10:20 Andrew Ammerlaan
2022-11-07 10:18 Andrew Ammerlaan
2022-11-07 10:18 Andrew Ammerlaan
2022-09-27 12:16 Andrew Ammerlaan
2022-09-27 12:16 Andrew Ammerlaan
2022-08-13 14:18 Andrew Ammerlaan
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=1709161021.d76a2cff990028e249d92d195f002174df3f58d3.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