public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org, Joseph Myers <joseph@codesourcery.com>
Subject: Re: Use MPFR 4.2.0, MPC 1.3.1 in build-many-glibcs.py
Date: Fri, 27 Jan 2023 15:17:45 -0300	[thread overview]
Message-ID: <de4b8d92-7fc5-4e90-4291-e17b12e652de@linaro.org> (raw)
In-Reply-To: <67204159-e875-bd81-b2ab-7e25c38921b8@codesourcery.com>



On 06/01/23 23:04, Joseph Myers wrote:
> This patch makes build-many-glibcs.py use the new MPFR 4.2.0 and MPC
> 1.3.1 releases.
> 
> Tested with build-many-glibcs.py (host-libraries, compilers and glibcs
> builds).

LGTM, thanks.

Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>

> 
> diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
> index f23c2d374b..50c51d49c0 100755
> --- a/scripts/build-many-glibcs.py
> +++ b/scripts/build-many-glibcs.py
> @@ -798,8 +798,8 @@ class Context(object):
>                              'glibc': 'vcs-mainline',
>                              'gmp': '6.2.1',
>                              'linux': '6.1',
> -                            'mpc': '1.2.1',
> -                            'mpfr': '4.1.0',
> +                            'mpc': '1.3.1',
> +                            'mpfr': '4.2.0',
>                              'mig': 'vcs-mainline',
>                              'gnumach': 'vcs-mainline',
>                              'hurd': 'vcs-mainline'}
> 

      parent reply	other threads:[~2023-01-27 18:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-07  2:04 Joseph Myers
2023-01-13 17:42 ` Ping " Joseph Myers
2023-01-20 17:14   ` Ping^2 " Joseph Myers
2023-01-27 18:17 ` Adhemerval Zanella Netto [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=de4b8d92-7fc5-4e90-4291-e17b12e652de@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --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).