From: Joseph Myers <joseph@codesourcery.com>
To: <libc-alpha@sourceware.org>
Subject: Use Linux 6.2 in build-many-glibcs.py
Date: Wed, 22 Feb 2023 18:00:01 +0000 [thread overview]
Message-ID: <b059bffe-a659-9f5-5613-11d6d94dde64@codesourcery.com> (raw)
This patch makes build-many-glibcs.py use Linux 6.2.
Tested with build-many-glibcs.py (host-libraries, compilers and glibcs
builds).
---
Avoiding a test failure for hppa also needs
<https://sourceware.org/pipermail/libc-alpha/2023-February/145805.html>.
diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
index bd212dbc82..29c10c2916 100755
--- a/scripts/build-many-glibcs.py
+++ b/scripts/build-many-glibcs.py
@@ -797,7 +797,7 @@ class Context(object):
'gcc': 'vcs-12',
'glibc': 'vcs-mainline',
'gmp': '6.2.1',
- 'linux': '6.1',
+ 'linux': '6.2',
'mpc': '1.3.1',
'mpfr': '4.2.0',
'mig': 'vcs-mainline',
--
Joseph S. Myers
joseph@codesourcery.com
next reply other threads:[~2023-02-22 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 18:00 Joseph Myers [this message]
2023-02-22 20:01 ` Adhemerval Zanella Netto
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=b059bffe-a659-9f5-5613-11d6d94dde64@codesourcery.com \
--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).