From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-patches:master commit in: 11.3.0/gentoo/
Date: Mon, 22 Aug 2022 01:41:37 +0000 (UTC) [thread overview]
Message-ID: <1661132491.5c3e52c3e7da07ee3ca18cb60f1e597a2cc0bf6f.sam@gentoo> (raw)
commit: 5c3e52c3e7da07ee3ca18cb60f1e597a2cc0bf6f
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 22 01:29:06 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Aug 22 01:41:31 2022 +0000
URL: https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=5c3e52c3
11.3.0: add another bug ref to glibc 2.36 patch
Bug: https://bugs.gentoo.org/864717
Signed-off-by: Sam James <sam <AT> gentoo.org>
11.3.0/gentoo/77_all_glibc_236.patch | 1 +
1 file changed, 1 insertion(+)
diff --git a/11.3.0/gentoo/77_all_glibc_236.patch b/11.3.0/gentoo/77_all_glibc_236.patch
index b398ec4..b9704e7 100644
--- a/11.3.0/gentoo/77_all_glibc_236.patch
+++ b/11.3.0/gentoo/77_all_glibc_236.patch
@@ -1,6 +1,7 @@
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=d2356ebb0084a0d80dbfe33040c9afe938c15d19
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=a55184ada8e2887ca94c0ab07027617885beafc9
https://bugs.gentoo.org/865879
+https://bugs.gentoo.org/864717
Fix build w/ glibc 2.36.
next reply other threads:[~2022-08-22 1:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 1:41 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-22 2:14 [gentoo-commits] proj/gcc-patches:master commit in: 11.3.0/gentoo/ Sam James
2022-08-22 1:41 Sam James
2022-08-18 20:03 Sam James
2022-01-08 4:09 Sam James
2022-01-08 3:49 Sam James
2022-01-08 3:49 Sam James
2021-12-28 5:57 Sam James
2021-12-18 22:00 Sam James
2021-12-18 22:00 Sam James
2021-12-18 22:00 Sam James
2021-12-07 20:06 Sam James
2021-12-02 15:03 David Seifert
2021-12-02 15:03 David Seifert
2021-12-02 15:03 David Seifert
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=1661132491.5c3e52c3e7da07ee3ca18cb60f1e597a2cc0bf6f.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