public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: Use binutils 2.39 branch in build-many-glibcs.py
Date: Thu, 18 Aug 2022 10:33:53 +0200	[thread overview]
Message-ID: <87pmgy0x3i.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2208172248190.417173@digraph.polyomino.org.uk> (Joseph Myers's message of "Wed, 17 Aug 2022 22:48:38 +0000")

* Joseph Myers:

> This patch makes build-many-glibcs.py use binutils 2.39 branch.
>
> Tested with build-many-glibcs.py (compilers and glibcs builds).  Note:
> binutils 2.39 shows the same failures for i686-linux-gnu-no-pie,
> x86_64-linux-gnu-no-pie and x86_64-linux-gnu-x32-no-pie building the
> glibc testsuite as binutils mainline does.
>
> diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
> index 070ac90fa1..98f02104a2 100755
> --- a/scripts/build-many-glibcs.py
> +++ b/scripts/build-many-glibcs.py
> @@ -789,7 +789,7 @@ class Context(object):
>  
>      def checkout(self, versions):
>          """Check out the desired component versions."""
> -        default_versions = {'binutils': 'vcs-2.38',
> +        default_versions = {'binutils': 'vcs-2.39',
>                              'gcc': 'vcs-12',
>                              'glibc': 'vcs-mainline',
>                              'gmp': '6.2.1',

Looks reasonable, thanks.

Florian


      reply	other threads:[~2022-08-18  8:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 22:48 Joseph Myers
2022-08-18  8:33 ` Florian Weimer [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pmgy0x3i.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=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).