From: Joseph Myers <joseph@codesourcery.com>
To: <libc-alpha@sourceware.org>
Subject: Use binutils 2.37 branch in build-many-glibcs.py
Date: Tue, 3 Aug 2021 00:30:40 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2108030030070.701636@digraph.polyomino.org.uk> (raw)
This patch makes build-many-glibcs.py use binutils 2.37 branch.
Tested with build-many-glibcs.py (compilers and glibcs builds).
diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
index 5a77af90a6..0322ed19a8 100755
--- a/scripts/build-many-glibcs.py
+++ b/scripts/build-many-glibcs.py
@@ -778,7 +778,7 @@ class Context(object):
def checkout(self, versions):
"""Check out the desired component versions."""
- default_versions = {'binutils': 'vcs-2.36',
+ default_versions = {'binutils': 'vcs-2.37',
'gcc': 'vcs-11',
'glibc': 'vcs-mainline',
'gmp': '6.2.1',
--
Joseph S. Myers
joseph@codesourcery.com
next reply other threads:[~2021-08-03 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 0:30 Joseph Myers [this message]
2021-08-09 16:49 ` Ping Re: Use binutils 2.37 branch in build-many-glibcs.py Joseph Myers
2021-08-09 16:53 ` H.J. Lu via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.22.394.2108030030070.701636@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).