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: Thu,  3 Feb 2022 05:15:28 +0000 (GMT)	[thread overview]
Message-ID: <20220203051528.239103858C2C@sourceware.org> (raw)

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

commit 6415fd2ddc5b48c3a3fe79805840f18ec4bf3d00
Author: Carlos O'Donell <carlos@redhat.com>
Date:   Thu Feb 3 00:06:38 2022 -0500

    Update install.texi, and regenerate INSTALL.

Diff:
---
 INSTALL             | 21 ++++++++++++---------
 manual/install.texi | 21 ++++++++++++---------
 2 files changed, 24 insertions(+), 18 deletions(-)

diff --git a/INSTALL b/INSTALL
index a9dc12fa31..63c022d6b9 100644
--- a/INSTALL
+++ b/INSTALL
@@ -502,7 +502,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 11.2 is the newest compiler
+     better code.  As of release time, GCC 12.0 is the newest compiler
      verified to work to build the GNU C Library.
 
      For PowerPC 64-bits little-endian (powerpc64le), a GCC version with
@@ -537,7 +537,7 @@ build the GNU C Library:
 
      You must use GNU 'binutils' (as and ld) to build the GNU C Library.
      No other assembler or linker has the necessary functionality at the
-     moment.  As of release time, GNU 'binutils' 2.35.1 is the newest
+     moment.  As of release time, GNU 'binutils' 2.37 is the newest
      verified to work to build the GNU C Library.
 
      For PowerPC 64-bits little-endian (powerpc64le), 'objcopy' is
@@ -553,7 +553,7 @@ build the GNU C Library:
      need this version of the 'texinfo' package.  Earlier versions do
      not understand all the tags used in the document, and the
      installation mechanism for the info files is not present or works
-     differently.  As of release time, 'texinfo' 6.7 is the newest
+     differently.  As of release time, 'texinfo' 6.8 is the newest
      verified to work to build the GNU C Library.
 
    * GNU 'awk' 3.1.2, or higher
@@ -561,20 +561,20 @@ build the GNU C Library:
      'awk' is used in several places to generate files.  Some 'gawk'
      extensions are used, including the 'asorti' function, which was
      introduced in version 3.1.2 of 'gawk'.  As of release time, 'gawk'
-     version 5.1 is the newest verified to work to build the GNU C
+     version 5.1.1 is the newest verified to work to build the GNU C
      Library.
 
    * GNU 'bison' 2.7 or later
 
      'bison' is used to generate the 'yacc' parser code in the 'intl'
-     subdirectory.  As of release time, 'bison' version 3.7.4 is the
+     subdirectory.  As of release time, 'bison' version 3.8.2 is the
      newest verified to work to build the GNU C Library.
 
    * Perl 5
 
      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.1 is the newest verified to work
+     release time 'perl' version 5.34.0 is the newest verified to work
      to build the GNU C Library.
 
    * GNU 'sed' 3.02 or newer
@@ -586,7 +586,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.9.6 is the newest verified to work for building and
+     Python 3.10.2 is the newest verified to work for building and
      testing the GNU C Library.
 
    * PExpect 4.0
@@ -594,7 +594,7 @@ build the GNU C Library:
      The pretty printer tests drive GDB through test programs and
      compare its output to the printers'.  PExpect is used to capture
      the output of GDB, and should be compatible with the Python version
-     in your system.  As of release time PExpect 4.8 is the newest
+     in your system.  As of release time PExpect 4.8.0 is the newest
      verified to work to test the pretty printers.
 
    * GDB 7.8 or later with support for Python 2.7/3.4 or later
@@ -603,7 +603,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.2 is the newest verified to work to test the
+     time GNU 'debugger' 11.1 is the newest verified to work to test the
      pretty printers.
 
      Unless Python, PExpect and GDB with Python support are present, the
@@ -667,6 +667,9 @@ components of the GNU C Library installation to be in '/lib' and some in
 Library with '--prefix=/usr'.  If you set some other prefix or allow it
 to default to '/usr/local', then all the components are installed there.
 
+   As of release time, Linux version 5.16 is the newest version verified
+to work to build the GNU C Library.
+
 Reporting Bugs
 ==============
 
diff --git a/manual/install.texi b/manual/install.texi
index accaef45fa..29c52f2927 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -543,7 +543,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 11.2 is the newest compiler verified to work to build
+release time, GCC 12.0 is the newest compiler verified to work to build
 @theglibc{}.
 
 For PowerPC 64-bits little-endian (powerpc64le), a GCC version with support
@@ -579,7 +579,7 @@ GNU @code{binutils} 2.25 or later
 
 You must use GNU @code{binutils} (as and ld) to build @theglibc{}.
 No other assembler or linker has the necessary functionality at the
-moment. As of release time, GNU @code{binutils} 2.35.1 is the newest
+moment. As of release time, GNU @code{binutils} 2.37 is the newest
 verified to work to build @theglibc{}.
 
 For PowerPC 64-bits little-endian (powerpc64le), @command{objcopy} is required
@@ -595,7 +595,7 @@ To correctly translate and install the Texinfo documentation you need
 this version of the @code{texinfo} package.  Earlier versions do not
 understand all the tags used in the document, and the installation
 mechanism for the info files is not present or works differently.
-As of release time, @code{texinfo} 6.7 is the newest verified to work
+As of release time, @code{texinfo} 6.8 is the newest verified to work
 to build @theglibc{}.
 
 @item
@@ -604,14 +604,14 @@ GNU @code{awk} 3.1.2, or higher
 @code{awk} is used in several places to generate files.
 Some @code{gawk} extensions are used, including the @code{asorti}
 function, which was introduced in version 3.1.2 of @code{gawk}.
-As of release time, @code{gawk} version 5.1 is the newest verified
+As of release time, @code{gawk} version 5.1.1 is the newest verified
 to work to build @theglibc{}.
 
 @item
 GNU @code{bison} 2.7 or later
 
 @code{bison} is used to generate the @code{yacc} parser code in the @file{intl}
-subdirectory.  As of release time, @code{bison} version 3.7.4 is the newest
+subdirectory.  As of release time, @code{bison} version 3.8.2 is the newest
 verified to work to build @theglibc{}.
 
 @item
@@ -619,7 +619,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.1 is the newest verified to work to
+time @code{perl} version 5.34.0 is the newest verified to work to
 build @theglibc{}.
 
 @item
@@ -633,7 +633,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.9.6 is the newest verified to work for building and testing
+3.10.2 is the newest verified to work for building and testing
 @theglibc{}.
 
 @item PExpect 4.0
@@ -641,7 +641,7 @@ Python is required to build @theglibc{}.  As of release time, Python
 The pretty printer tests drive GDB through test programs and compare
 its output to the printers'.  PExpect is used to capture the output of
 GDB, and should be compatible with the Python version in your system.
-As of release time PExpect 4.8 is the newest verified to work to test
+As of release time PExpect 4.8.0 is the newest verified to work to test
 the pretty printers.
 
 @item
@@ -651,7 +651,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.2 is the newest verified to work to test the pretty printers.
+11.1 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
@@ -728,6 +728,9 @@ if you configure @theglibc{} with @samp{--prefix=/usr}.  If you set some other
 prefix or allow it to default to @file{/usr/local}, then all the
 components are installed there.
 
+As of release time, Linux version 5.16 is the newest version verified
+to work to build @theglibc{}.
+
 @node Reporting Bugs
 @appendixsec Reporting Bugs
 @cindex reporting bugs


             reply	other threads:[~2022-02-03  5:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03  5:15 Carlos O'Donell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-01  1:12 Carlos O'Donell
2022-07-29 21:57 Carlos O'Donell
2021-08-01 20:49 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=20220203051528.239103858C2C@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: 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).