From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pypy3_10-exe/
Date: Fri, 8 Dec 2023 07:44:02 +0000 (UTC) [thread overview]
Message-ID: <1702021405.7f8ab7568599ba4335a09e3167be8d676911ffe0.sam@gentoo> (raw)
commit: 7f8ab7568599ba4335a09e3167be8d676911ffe0
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Dec 8 07:42:58 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Dec 8 07:43:25 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7f8ab756
dev-python/pypy3_10-exe: workaround C warnings for now
Upstream are working on it and nearly have it fixed, but the patches are
large and not worth backporting until it's completely fixed at least.
Add a workaround for now :(
Bug: https://foss.heptapod.net/pypy/pypy/-/issues/4042
Bug: https://bugs.gentoo.org/918971
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/pypy3_10-exe/pypy3_10-exe-7.3.13_p3.ebuild | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/dev-python/pypy3_10-exe/pypy3_10-exe-7.3.13_p3.ebuild b/dev-python/pypy3_10-exe/pypy3_10-exe-7.3.13_p3.ebuild
index faf6b8a1e385..9eec2da0971d 100644
--- a/dev-python/pypy3_10-exe/pypy3_10-exe-7.3.13_p3.ebuild
+++ b/dev-python/pypy3_10-exe/pypy3_10-exe-7.3.13_p3.ebuild
@@ -3,7 +3,7 @@
EAPI=8
-inherit check-reqs pax-utils toolchain-funcs
+inherit check-reqs flag-o-matic pax-utils toolchain-funcs
PYPY_PV=${PV%_p*}
PYVER=3.10
@@ -70,6 +70,10 @@ src_prepare() {
src_configure() {
tc-export CC
+ # Yes, yuck, but it's being worked on upstream (bug #918971).
+ # https://foss.heptapod.net/pypy/pypy/-/issues/4042
+ append-flags $(test-flags-CC -Wno-error=incompatible-pointer-types)
+
local jit_backend
if use jit; then
jit_backend='--jit-backend='
next reply other threads:[~2023-12-08 7:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 7:44 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-15 15:04 [gentoo-commits] repo/gentoo:master commit in: dev-python/pypy3_10-exe/ Michał Górny
2024-09-15 15:04 Michał Górny
2024-08-29 16:29 Michał Górny
2024-04-25 3:39 Michał Górny
2024-04-24 17:16 Sam James
2024-04-24 17:16 Sam James
2024-04-24 15:08 Michał Górny
2024-02-03 15:02 Michał Górny
2024-02-03 14:03 Arthur Zamarin
2024-02-03 13:52 Sam James
2024-01-21 6:21 Michał Górny
2024-01-21 4:29 Sam James
2024-01-21 2:44 Sam James
2024-01-15 21:24 Michał Górny
2024-01-03 19:49 Michał Górny
2023-12-25 20:26 Michał Górny
2023-12-15 16:19 Michał Górny
2023-12-15 15:50 Arthur Zamarin
2023-12-15 11:36 Arthur Zamarin
2023-12-08 5:17 Michał Górny
2023-12-01 21:58 Michał Górny
2023-11-22 7:49 Michał Górny
2023-11-21 19:05 Michał Górny
2023-11-02 12:58 Michał Górny
2023-09-30 8:27 Michał Górny
2023-08-24 12:47 Michał Górny
2023-07-21 12:46 Michał Górny
2023-07-15 18:02 Arthur Zamarin
2023-07-11 8:43 Jakov Smolić
2023-06-19 5:14 Michał Górny
2023-06-16 17:03 Michał Górny
2023-05-31 11:42 Michał Górny
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=1702021405.7f8ab7568599ba4335a09e3167be8d676911ffe0.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