public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] Update install.texi, and regenerate INSTALL. Date: Sun, 1 Aug 2021 20:49:19 +0000 (GMT) [thread overview] Message-ID: <20210801204919.2ED863855010@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=06eae99ab40becdb136a0d4aab78c96afb4fcaa5 commit 06eae99ab40becdb136a0d4aab78c96afb4fcaa5 Author: Carlos O'Donell <carlos@redhat.com> Date: Sun Aug 1 16:36:25 2021 -0400 Update install.texi, and regenerate INSTALL. Diff: --- INSTALL | 8 ++++---- manual/install.texi | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/INSTALL b/INSTALL index 56ed01d438..02dcf6b1ca 100644 --- a/INSTALL +++ b/INSTALL @@ -491,7 +491,7 @@ build the GNU C Library: GCC 6.2 or higher is required. In general it is recommended to use the newest version of the compiler that is known to work for building the GNU C Library, as newer compilers usually produce - better code. As of release time, GCC 10.2 is the newest compiler + better code. As of release time, GCC 11.2 is the newest compiler verified to work to build the GNU C Library. For PowerPC 64-bits little-endian (powerpc64le), a GCC version with @@ -563,7 +563,7 @@ build the GNU C Library: Perl is not required, but if present it is used in some tests and the 'mtrace' program, to build the GNU C Library manual. As of - release time 'perl' version 5.32.0 is the newest verified to work + release time 'perl' version 5.32.1 is the newest verified to work to build the GNU C Library. * GNU 'sed' 3.02 or newer @@ -575,7 +575,7 @@ build the GNU C Library: * Python 3.4 or later Python is required to build the GNU C Library. As of release time, - Python 3.8.6 is the newest verified to work for building and + Python 3.9.6 is the newest verified to work for building and testing the GNU C Library. * PExpect 4.0 @@ -592,7 +592,7 @@ build the GNU C Library: use the pretty printers. Notice that your system having Python available doesn't imply that GDB supports it, nor that your system's Python and GDB's have the same version. As of release - time GNU 'debugger' 10.1 is the newest verified to work to test the + time GNU 'debugger' 10.2 is the newest verified to work to test the pretty printers. Unless Python, PExpect and GDB with Python support are present, the diff --git a/manual/install.texi b/manual/install.texi index 254a8a9a79..46f73b538d 100644 --- a/manual/install.texi +++ b/manual/install.texi @@ -533,7 +533,7 @@ GCC 6.2 or newer GCC 6.2 or higher is required. In general it is recommended to use the newest version of the compiler that is known to work for building @theglibc{}, as newer compilers usually produce better code. As of -release time, GCC 10.2 is the newest compiler verified to work to build +release time, GCC 11.2 is the newest compiler verified to work to build @theglibc{}. For PowerPC 64-bits little-endian (powerpc64le), a GCC version with support @@ -609,7 +609,7 @@ Perl 5 Perl is not required, but if present it is used in some tests and the @code{mtrace} program, to build the @glibcadj{} manual. As of release -time @code{perl} version 5.32.0 is the newest verified to work to +time @code{perl} version 5.32.1 is the newest verified to work to build @theglibc{}. @item @@ -623,7 +623,7 @@ with any version of @code{sed}. As of release time, @code{sed} version Python 3.4 or later Python is required to build @theglibc{}. As of release time, Python -3.8.6 is the newest verified to work for building and testing +3.9.6 is the newest verified to work for building and testing @theglibc{}. @item PExpect 4.0 @@ -641,7 +641,7 @@ GDB itself needs to be configured with Python support in order to use the pretty printers. Notice that your system having Python available doesn't imply that GDB supports it, nor that your system's Python and GDB's have the same version. As of release time GNU @code{debugger} -10.1 is the newest verified to work to test the pretty printers. +10.2 is the newest verified to work to test the pretty printers. Unless Python, PExpect and GDB with Python support are present, the printer tests will report themselves as @code{UNSUPPORTED}. Notice
next reply other threads:[~2021-08-01 20:49 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-01 20:49 Carlos O'Donell [this message] 2022-02-03 5:15 Carlos O'Donell 2022-07-29 21:57 Carlos O'Donell 2023-02-01 1:12 Carlos O'Donell
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=20210801204919.2ED863855010@sourceware.org \ --to=carlos@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: linkBe 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).