public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "David Roman" <davidroman96@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: dev-lang/swift/
Date: Fri, 17 Jan 2025 09:41:37 +0000 (UTC)	[thread overview]
Message-ID: <1736970809.1e8cb85c79c4feabd23e999cda27c1cfbdb90cc9.davidroman@gentoo> (raw)

commit:     1e8cb85c79c4feabd23e999cda27c1cfbdb90cc9
Author:     Itai Ferber <itai <AT> itaiferber <DOT> net>
AuthorDate: Wed Jan 15 19:50:17 2025 +0000
Commit:     David Roman <davidroman96 <AT> gmail <DOT> com>
CommitDate: Wed Jan 15 19:53:29 2025 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=1e8cb85c

dev-lang/swift: remove dev-cpp/tbb as a strong blocker for Swift 6

Swift 6 builds with `dev-cpp/tbb` installed on systems with
>=libstdc++-11 (the minimum version currently supported by Gentoo) as
long as it's bootstrapped by swift-5.10.1-r3 or later (which has a patch
backported from Swift 6 which prevents `<execution>` from getting picked
up).

Bug: https://bugs.gentoo.org/947141
Signed-off-by: Itai Ferber <itai <AT> itaiferber.net>

 dev-lang/swift/swift-6.0.1-r1.ebuild | 13 +------------
 dev-lang/swift/swift-6.0.1.ebuild    | 13 +------------
 dev-lang/swift/swift-6.0.2.ebuild    | 13 +------------
 dev-lang/swift/swift-6.0.3.ebuild    | 13 +------------
 4 files changed, 4 insertions(+), 48 deletions(-)

diff --git a/dev-lang/swift/swift-6.0.1-r1.ebuild b/dev-lang/swift/swift-6.0.1-r1.ebuild
index 86dc9abab..672e8c12a 100644
--- a/dev-lang/swift/swift-6.0.1-r1.ebuild
+++ b/dev-lang/swift/swift-6.0.1-r1.ebuild
@@ -93,6 +93,7 @@ BDEPEND="
 	>=dev-util/patchelf-0.18
 	>=dev-vcs/git-2.39
 	>=sys-apps/coreutils-9
+	>=sys-devel/gcc-11
 	>=sys-libs/ncurses-6
 	>=sys-libs/zlib-1.3
 	|| (
@@ -109,18 +110,6 @@ BDEPEND="
 	' python3_{12..13})
 "
 
-# Swift 6 upstream currently doesn't build with oneTBB installed because Swift's
-# `libstdcxx.h` includes `<execution>`, which, in combination with recent
-# `libstdc++` versions, causes `tbb/execution` to get picked up; this results in
-# a circular dependency back on the stdlib, failing the build.
-#
-# See:
-# * https://bugs.gentoo.org/947141
-# * https://github.com/swiftlang/swift/issues/76166
-BDEPEND+="
-	!!dev-cpp/tbb
-"
-
 # Adapted from `flag-o-matic.eclass`'s `raw-ldflags`: turns GCC-style flags
 # (`-Wl,-foo`) into Clang-style flags (`-Xlinker -foo`).
 clang-ldflags() {

diff --git a/dev-lang/swift/swift-6.0.1.ebuild b/dev-lang/swift/swift-6.0.1.ebuild
index 085c043de..630ea1e18 100644
--- a/dev-lang/swift/swift-6.0.1.ebuild
+++ b/dev-lang/swift/swift-6.0.1.ebuild
@@ -92,6 +92,7 @@ BDEPEND="
 	>=dev-util/patchelf-0.18
 	>=dev-vcs/git-2.39
 	>=sys-apps/coreutils-9
+	>=sys-devel/gcc-11
 	>=sys-libs/ncurses-6
 	>=sys-libs/zlib-1.3
 	|| (
@@ -108,18 +109,6 @@ BDEPEND="
 	' python3_{12..13})
 "
 
-# Swift 6 upstream currently doesn't build with oneTBB installed because Swift's
-# `libstdcxx.h` includes `<execution>`, which, in combination with recent
-# `libstdc++` versions, causes `tbb/execution` to get picked up; this results in
-# a circular dependency back on the stdlib, failing the build.
-#
-# See:
-# * https://bugs.gentoo.org/947141
-# * https://github.com/swiftlang/swift/issues/76166
-BDEPEND+="
-	!!dev-cpp/tbb
-"
-
 # Adapted from `flag-o-matic.eclass`'s `raw-ldflags`: turns GCC-style flags
 # (`-Wl,-foo`) into Clang-style flags (`-Xlinker -foo`).
 clang-ldflags() {

diff --git a/dev-lang/swift/swift-6.0.2.ebuild b/dev-lang/swift/swift-6.0.2.ebuild
index 86dc9abab..672e8c12a 100644
--- a/dev-lang/swift/swift-6.0.2.ebuild
+++ b/dev-lang/swift/swift-6.0.2.ebuild
@@ -93,6 +93,7 @@ BDEPEND="
 	>=dev-util/patchelf-0.18
 	>=dev-vcs/git-2.39
 	>=sys-apps/coreutils-9
+	>=sys-devel/gcc-11
 	>=sys-libs/ncurses-6
 	>=sys-libs/zlib-1.3
 	|| (
@@ -109,18 +110,6 @@ BDEPEND="
 	' python3_{12..13})
 "
 
-# Swift 6 upstream currently doesn't build with oneTBB installed because Swift's
-# `libstdcxx.h` includes `<execution>`, which, in combination with recent
-# `libstdc++` versions, causes `tbb/execution` to get picked up; this results in
-# a circular dependency back on the stdlib, failing the build.
-#
-# See:
-# * https://bugs.gentoo.org/947141
-# * https://github.com/swiftlang/swift/issues/76166
-BDEPEND+="
-	!!dev-cpp/tbb
-"
-
 # Adapted from `flag-o-matic.eclass`'s `raw-ldflags`: turns GCC-style flags
 # (`-Wl,-foo`) into Clang-style flags (`-Xlinker -foo`).
 clang-ldflags() {

diff --git a/dev-lang/swift/swift-6.0.3.ebuild b/dev-lang/swift/swift-6.0.3.ebuild
index 86dc9abab..672e8c12a 100644
--- a/dev-lang/swift/swift-6.0.3.ebuild
+++ b/dev-lang/swift/swift-6.0.3.ebuild
@@ -93,6 +93,7 @@ BDEPEND="
 	>=dev-util/patchelf-0.18
 	>=dev-vcs/git-2.39
 	>=sys-apps/coreutils-9
+	>=sys-devel/gcc-11
 	>=sys-libs/ncurses-6
 	>=sys-libs/zlib-1.3
 	|| (
@@ -109,18 +110,6 @@ BDEPEND="
 	' python3_{12..13})
 "
 
-# Swift 6 upstream currently doesn't build with oneTBB installed because Swift's
-# `libstdcxx.h` includes `<execution>`, which, in combination with recent
-# `libstdc++` versions, causes `tbb/execution` to get picked up; this results in
-# a circular dependency back on the stdlib, failing the build.
-#
-# See:
-# * https://bugs.gentoo.org/947141
-# * https://github.com/swiftlang/swift/issues/76166
-BDEPEND+="
-	!!dev-cpp/tbb
-"
-
 # Adapted from `flag-o-matic.eclass`'s `raw-ldflags`: turns GCC-style flags
 # (`-Wl,-foo`) into Clang-style flags (`-Xlinker -foo`).
 clang-ldflags() {


             reply	other threads:[~2025-01-17  9:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17  9:41 David Roman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-08 11:18 [gentoo-commits] repo/proj/guru:master commit in: dev-lang/swift/ Lucio Sauer
2025-02-11 11:12 David Roman
2025-02-11 11:12 David Roman
2025-01-13 11:38 David Roman
2024-10-13 14:51 David Roman
2024-10-13 14:51 David Roman
2024-10-13 14:51 David Roman
2024-10-13 14:51 David Roman
2024-10-13 14:51 David Roman
2024-10-13 14:51 David Roman
2024-09-14  0:43 David Roman
2024-09-14  0:43 David Roman
2024-08-10 20:34 Lucio Sauer
2024-08-10 20:34 Lucio Sauer
2024-08-10 20:34 Lucio Sauer
2024-08-10 20:34 Lucio Sauer
2024-08-10 20:34 Lucio Sauer
2024-08-10 20:34 Lucio Sauer
2024-07-17  8:40 David Roman
2024-07-17  8:40 David Roman
2024-07-01 13:50 David Roman

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=1736970809.1e8cb85c79c4feabd23e999cda27c1cfbdb90cc9.davidroman@gentoo \
    --to=davidroman96@gmail.com \
    --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