unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: Use Linux 5.12 and GCC 11 branch in build-many-glibcs.py
Date: Tue, 27 Apr 2021 06:28:47 +0200	[thread overview]
Message-ID: <87czugqrk0.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2104262354320.641239@digraph.polyomino.org.uk> (Joseph Myers's message of "Mon, 26 Apr 2021 23:54:53 +0000")

* Joseph Myers:

> This patch makes build-many-glibcs.py use Linux 5.12 and GCC 11
> branch.
>
> Tested with build-many-glibcs.py (host-libraries, compilers and glibcs
> builds).
>
> diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
> index 580d25e8ee..41639f26f7 100755
> --- a/scripts/build-many-glibcs.py
> +++ b/scripts/build-many-glibcs.py
> @@ -766,10 +766,10 @@ class Context(object):
>      def checkout(self, versions):
>          """Check out the desired component versions."""
>          default_versions = {'binutils': 'vcs-2.36',
> -                            'gcc': 'vcs-10',
> +                            'gcc': 'vcs-11',
>                              'glibc': 'vcs-mainline',
>                              'gmp': '6.2.1',
> -                            'linux': '5.11',
> +                            'linux': '5.12',
>                              'mpc': '1.2.1',
>                              'mpfr': '4.1.0',
>                              'mig': 'vcs-mainline',

Thanks, looks good.

Florian


      reply	other threads:[~2021-04-27  4:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 23:54 Use Linux 5.12 and GCC 11 branch in build-many-glibcs.py Joseph Myers
2021-04-27  4:28 ` Florian Weimer via Libc-alpha [this message]

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=87czugqrk0.fsf@oldenburg.str.redhat.com \
    --to=libc-alpha@sourceware.org \
    --cc=fweimer@redhat.com \
    --cc=joseph@codesourcery.com \
    /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).