public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/prefix:master commit in: sys-devel/gcc/
Date: Wed, 10 Nov 2021 04:38:26 +0000 (UTC)	[thread overview]
Message-ID: <1636519100.b78850ca7a012cca0dd250470d228eee18d2a429.sam@gentoo> (raw)

commit:     b78850ca7a012cca0dd250470d228eee18d2a429
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 10 04:38:20 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Nov 10 04:38:20 2021 +0000
URL:        https://gitweb.gentoo.org/repo/proj/prefix.git/commit/?id=b78850ca

sys-devel/gcc: add macOS 12 patch to gcc-11_pre20210226

We should probably do a newer snapshot soon though.

Package-Manager: Portage-3.0.21-prefix, Repoman-3.0.3
Signed-off-by: Sam James <sam <AT> gentoo.org>

 sys-devel/gcc/gcc-11_pre20210226.ebuild | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/sys-devel/gcc/gcc-11_pre20210226.ebuild b/sys-devel/gcc/gcc-11_pre20210226.ebuild
index e423f88664..3aa29c8610 100644
--- a/sys-devel/gcc/gcc-11_pre20210226.ebuild
+++ b/sys-devel/gcc/gcc-11_pre20210226.ebuild
@@ -53,6 +53,9 @@ src_prepare() {
 	# found
 	sed -i -e 's/ALL_SPPFLAGS/ALL_CPPFLAGS/' \
 		gcc/config/aarch64/t-aarch64 || die
+
+	# allow building with macOS 12
+	eapply -p1 "${FILESDIR}"/${PN}-10.3.0-monterey.patch
 }
 
 src_configure() {


             reply	other threads:[~2021-11-10  4:38 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10  4:38 Sam James [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-09 15:54 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-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=1636519100.b78850ca7a012cca0dd250470d228eee18d2a429.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