public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Joseph Myers <jsm28@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Use MPFR 4.2.0, MPC 1.3.1 in build-many-glibcs.py
Date: Fri, 27 Jan 2023 18:27:44 +0000 (GMT)	[thread overview]
Message-ID: <20230127182744.06DBA385843E@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=d659442e01e659ad6400b29a0e096639853812c6

commit d659442e01e659ad6400b29a0e096639853812c6
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Fri Jan 27 18:27:26 2023 +0000

    Use MPFR 4.2.0, MPC 1.3.1 in build-many-glibcs.py
    
    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).

Diff:
---
 scripts/build-many-glibcs.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
index ae1346c96d..09264c8b5f 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'}

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

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230127182744.06DBA385843E@sourceware.org \
    --to=jsm28@sourceware.org \
    --cc=glibc-cvs@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).