public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/prefix:master commit in: sys-devel/gcc/
Date: Sat,  9 Mar 2024 15:54:24 +0000 (UTC)	[thread overview]
Message-ID: <1709999615.294ac693f187e17e568400199f4edd1d74e277eb.grobian@gentoo> (raw)

commit:     294ac693f187e17e568400199f4edd1d74e277eb
Author:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Sat Mar  9 15:53:35 2024 +0000
Commit:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Sat Mar  9 15:53:35 2024 +0000
URL:        https://gitweb.gentoo.org/repo/proj/prefix.git/commit/?id=294ac693

sys-devel/gcc-14.0.1: dekeyword, better not to use it (yet)

Signed-off-by: Fabian Groffen <grobian <AT> gentoo.org>

 sys-devel/gcc/gcc-14.0.1_pre20240225.ebuild | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/sys-devel/gcc/gcc-14.0.1_pre20240225.ebuild b/sys-devel/gcc/gcc-14.0.1_pre20240225.ebuild
index 65946e6d92..a1b9fee8c4 100644
--- a/sys-devel/gcc/gcc-14.0.1_pre20240225.ebuild
+++ b/sys-devel/gcc/gcc-14.0.1_pre20240225.ebuild
@@ -13,7 +13,9 @@ inherit toolchain
 
 # Don't keyword live ebuilds
 if ! tc_is_live && [[ -z ${TOOLCHAIN_USE_GIT_PATCHES} ]] ; then
-	KEYWORDS="~amd64-linux ~x86-linux ~arm64-macos ~ppc-macos ~x64-macos ~x64-solaris"
+	#KEYWORDS="~amd64-linux ~x86-linux ~arm64-macos ~ppc-macos ~x64-macos ~x64-solaris"
+	# can't bootstrap from this using clang's libc++, better not use it
+	KEYWORDS=""
 fi
 
 # use alternate source for Apple M1 (also works for x86_64)


             reply	other threads:[~2024-03-09 15:54 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-09 15:54 Fabian Groffen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-30  9:08 [gentoo-commits] repo/proj/prefix:master commit in: sys-devel/gcc/ Fabian Groffen
2024-09-30  9:08 Fabian Groffen
2024-09-29  8:18 Fabian Groffen
2024-08-10 14:48 Fabian Groffen
2024-07-18  6:42 Fabian Groffen
2024-07-17 12:01 Fabian Groffen
2024-05-27 17:04 Fabian Groffen
2024-05-27  7:14 Fabian Groffen
2024-03-08 21:13 Fabian Groffen
2024-02-06 13:16 Fabian Groffen
2024-01-14 20:36 Fabian Groffen
2024-01-14 10:17 Fabian Groffen
2023-09-10  7:20 Fabian Groffen
2023-05-01  6:30 Fabian Groffen
2023-04-27 10:27 Fabian Groffen
2023-04-26 19:21 Fabian Groffen
2023-04-26 17:57 Fabian Groffen
2023-04-24 20:12 Sam James
2023-02-19 18:53 Sam James
2022-11-06 12:05 Fabian Groffen
2022-10-03 17:26 Fabian Groffen
2022-08-02 13:06 Fabian Groffen
2022-06-16  5:52 Fabian Groffen
2022-06-08 11:04 Fabian Groffen
2021-11-10  4:38 Sam James
2021-11-09  7:22 Sam James
2021-09-12  8:47 Sam James
2021-06-21  5:59 Sam James
2021-06-08  6:18 Fabian Groffen
2021-02-20 14:13 Fabian Groffen
2021-02-07 19:23 Fabian Groffen
2021-02-06 16:30 Fabian Groffen
2021-01-10 19:51 Fabian Groffen
2021-01-06 12:00 Fabian Groffen
2021-01-04 16:07 Fabian Groffen
2020-12-22 21:30 Fabian Groffen
2020-11-26 20:49 Fabian Groffen
2020-11-26 20:03 Fabian Groffen
2020-11-26 18:58 Fabian Groffen
2020-11-23 20:55 Fabian Groffen
2020-11-23 20:25 Fabian Groffen
2020-11-22 17:37 Fabian Groffen
2020-01-08 19:21 Fabian Groffen
2019-06-07 12:37 Michael Haubenwallner
2019-06-07  8:32 Michael Haubenwallner
2019-03-13 14:14 Fabian Groffen
2019-03-13 14:14 Fabian Groffen
2019-01-30 10:54 Fabian Groffen
2018-12-17 20:01 Fabian Groffen
2018-06-27  7:09 Fabian Groffen
2018-06-22 13:16 Michael Haubenwallner
2018-06-21  7:30 Fabian Groffen
2018-06-08 13:06 Fabian Groffen
2018-06-08  5:46 Fabian Groffen
2018-06-07 10:49 Fabian Groffen
2018-06-06 13:47 Fabian Groffen
2018-01-15 19:38 Fabian Groffen
2017-12-29 22:08 Michael Haubenwallner
2017-12-12 18:53 Fabian Groffen
2017-09-13 14:06 Michael Haubenwallner
2016-10-03 12:48 Fabian Groffen
2016-04-28 10:57 Michael Haubenwallner
2016-04-18  8:07 Michael Haubenwallner
2016-03-28 11:11 Alexey Shvetsov
2016-03-28  9:19 Alexey Shvetsov
2016-02-03 15:06 Alexey Shvetsov

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=1709999615.294ac693f187e17e568400199f4edd1d74e277eb.grobian@gentoo \
    --to=grobian@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