From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: llvm-core/flang/
Date: Thu, 29 May 2025 04:22:09 +0000 (UTC) [thread overview]
Message-ID: <1748492172.73c3423b39e38f6dbdad165fade9ba5d2ecb796a.mgorny@gentoo> (raw)
commit: 73c3423b39e38f6dbdad165fade9ba5d2ecb796a
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Wed May 28 16:06:30 2025 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Thu May 29 04:16:12 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=73c3423b
llvm-core/flang: Enable py3.14 in 21.0.0.9999
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
llvm-core/flang/flang-21.0.0.9999.ebuild | 2 +-
llvm-core/flang/flang-21.0.0_pre20250528.ebuild | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/llvm-core/flang/flang-21.0.0.9999.ebuild b/llvm-core/flang/flang-21.0.0.9999.ebuild
index 9c3d3f4568bf..2561b1b7570e 100644
--- a/llvm-core/flang/flang-21.0.0.9999.ebuild
+++ b/llvm-core/flang/flang-21.0.0.9999.ebuild
@@ -3,7 +3,7 @@
EAPI=8
-PYTHON_COMPAT=( python3_{11..13} )
+PYTHON_COMPAT=( python3_{11..14} )
inherit cmake llvm.org python-any-r1
DESCRIPTION="LLVM's Fortran frontend"
diff --git a/llvm-core/flang/flang-21.0.0_pre20250528.ebuild b/llvm-core/flang/flang-21.0.0_pre20250528.ebuild
index 9c3d3f4568bf..2561b1b7570e 100644
--- a/llvm-core/flang/flang-21.0.0_pre20250528.ebuild
+++ b/llvm-core/flang/flang-21.0.0_pre20250528.ebuild
@@ -3,7 +3,7 @@
EAPI=8
-PYTHON_COMPAT=( python3_{11..13} )
+PYTHON_COMPAT=( python3_{11..14} )
inherit cmake llvm.org python-any-r1
DESCRIPTION="LLVM's Fortran frontend"
next reply other threads:[~2025-05-29 4:22 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 4:22 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-04 20:19 [gentoo-commits] repo/gentoo:master commit in: llvm-core/flang/ Michał Górny
2025-11-01 12:02 Michał Górny
2025-10-28 11:37 Michał Górny
2025-10-22 19:12 Michał Górny
2025-10-21 18:43 Michał Górny
2025-10-11 19:54 Michał Górny
2025-10-08 17:28 Michał Górny
2025-10-04 9:16 Michał Górny
2025-10-03 11:43 Michał Górny
2025-10-01 6:35 Michał Górny
2025-09-24 16:18 Michał Górny
2025-09-24 2:27 Michał Górny
2025-09-21 2:44 Michał Górny
2025-09-10 11:47 Michał Górny
2025-09-07 19:47 Michał Górny
2025-08-31 13:28 Michał Górny
2025-08-26 19:38 Michał Górny
2025-08-21 8:22 Michał Górny
2025-08-21 8:18 Michał Górny
2025-08-16 13:51 Michał Górny
2025-08-12 17:09 Michał Górny
2025-08-09 9:47 Michał Górny
2025-08-02 10:29 Michał Górny
2025-07-29 19:04 Michał Górny
2025-07-26 19:53 Michał Górny
2025-07-22 9:20 Michał Górny
2025-07-20 14:15 Michał Górny
2025-07-19 6:50 Michał Górny
2025-07-13 20:03 Michał Górny
2025-06-28 15:03 Michał Górny
2025-06-28 14:55 Michał Górny
2025-06-08 0:10 Sam James
2025-06-07 18:05 Michał Górny
2025-06-07 16:32 Michał Górny
2025-05-28 11:54 Michał Górny
2025-05-28 10:50 Michał Górny
2025-05-24 14:02 Michał Górny
2025-05-24 11:56 Michał Górny
2025-05-17 12:59 Michał Górny
2025-05-17 5:31 Michał Górny
2025-05-10 13:03 Michał Górny
2025-05-03 19:42 Michał Górny
2025-04-26 15:59 Michał Górny
2025-04-20 11:50 Michał Górny
2025-04-19 6:29 Michał Górny
2025-04-15 10:15 Michał Górny
2025-04-12 4:57 Michał Górny
2025-04-05 12:24 Michał Górny
2025-03-29 10:27 Michał Górny
2025-03-22 10:43 Michał Górny
2025-03-17 20:13 Michał Górny
2025-03-16 17:41 Michał Górny
2025-03-11 14:56 Michał Górny
2025-03-05 10:39 Michał Górny
2025-03-01 12:58 Michał Górny
2025-03-01 8:34 Michał Górny
2025-02-25 14:03 Michał Górny
2025-02-25 8:51 Michał Górny
2025-02-24 14:14 Michał Górny
2025-02-22 15:19 Michał Górny
2025-02-21 18:17 Michał Górny
2025-02-17 20:47 Michał Górny
2025-02-17 20:47 Michał Górny
2025-02-16 2:37 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=1748492172.73c3423b39e38f6dbdad165fade9ba5d2ecb796a.mgorny@gentoo \
--to=mgorny@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