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: Wed,  1 Feb 2023 01:12:38 +0000 (GMT)	[thread overview]
Message-ID: <20230201011238.7D7AE3858434@sourceware.org> (raw)

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

commit 5199024232eb9da46150c73af3a198185aa48aa6
Author: Carlos O'Donell <carlos@redhat.com>
Date:   Tue Jan 31 17:15:24 2023 -0500

    Update install.texi, and regenerate INSTALL.

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

diff --git a/INSTALL b/INSTALL
index 659f75a97f..970d6627e2 100644
--- a/INSTALL
+++ b/INSTALL
@@ -500,7 +500,7 @@ build the GNU C Library:
 
    * GNU 'make' 4.0 or newer
 
-     As of relase time, GNU 'make' 4.3 is the newest verified to work to
+     As of relase time, GNU 'make' 4.4 is the newest verified to work to
      build the GNU C Library.
 
    * GCC 6.2 or newer
@@ -508,7 +508,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 12.1 is the newest compiler
+     better code.  As of release time, GCC 13.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
@@ -543,7 +543,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.38 is the newest
+     moment.  As of release time, GNU 'binutils' 2.39 is the newest
      verified to work to build the GNU C Library.
 
      For PowerPC 64-bits little-endian (powerpc64le), 'objcopy' is
@@ -559,7 +559,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.8 is the newest
+     differently.  As of release time, 'texinfo' 7.0.2 is the newest
      verified to work to build the GNU C Library.
 
    * GNU 'awk' 3.1.2, or higher
@@ -580,7 +580,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.34.1 is the newest verified to work
+     release time 'perl' version 5.36.0 is the newest verified to work
      to build the GNU C Library.
 
    * GNU 'sed' 3.02 or newer
@@ -592,8 +592,8 @@ 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.10.5 is the newest verified to work for building and
-     testing the GNU C Library.
+     Python 3.11 is the newest verified to work for building and testing
+     the GNU C Library.
 
    * PExpect 4.0
 
@@ -625,7 +625,7 @@ and if you change any of the message translation files you will need
 
    * GNU 'gettext' 0.10.36 or later
 
-     As of release time, GNU 'gettext' version 0.21 is the newest
+     As of release time, GNU 'gettext' version 0.21.1 is the newest
      version verified to work to build the GNU C Library.
 
 You may also need these packages if you upgrade your source tree using
@@ -673,7 +673,7 @@ 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.18 is the newest stable version
+   As of release time, Linux version 6.1.5 is the newest stable version
 verified to work to build the GNU C Library.
 
 Reporting Bugs
diff --git a/manual/install.texi b/manual/install.texi
index c775005581..260f8a5c82 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -540,7 +540,7 @@ build @theglibc{}:
 @item
 GNU @code{make} 4.0 or newer
 
-As of relase time, GNU @code{make} 4.3 is the newest verified to work
+As of relase time, GNU @code{make} 4.4 is the newest verified to work
 to build @theglibc{}.
 
 @item
@@ -549,7 +549,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 12.1 is the newest compiler verified to work to build
+release time, GCC 13.0 is the newest compiler verified to work to build
 @theglibc{}.
 
 For PowerPC 64-bits little-endian (powerpc64le), a GCC version with support
@@ -585,7 +585,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.38 is the newest
+moment. As of release time, GNU @code{binutils} 2.39 is the newest
 verified to work to build @theglibc{}.
 
 For PowerPC 64-bits little-endian (powerpc64le), @command{objcopy} is required
@@ -601,7 +601,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.8 is the newest verified to work
+As of release time, @code{texinfo} 7.0.2 is the newest verified to work
 to build @theglibc{}.
 
 @item
@@ -625,7 +625,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.34.1 is the newest verified to work to
+time @code{perl} version 5.36.0 is the newest verified to work to
 build @theglibc{}.
 
 @item
@@ -639,7 +639,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.10.5 is the newest verified to work for building and testing
+3.11 is the newest verified to work for building and testing
 @theglibc{}.
 
 @item PExpect 4.0
@@ -680,7 +680,7 @@ and if you change any of the message translation files you will need
 @item
 GNU @code{gettext} 0.10.36 or later
 
-As of release time, GNU @code{gettext} version 0.21 is the newest
+As of release time, GNU @code{gettext} version 0.21.1 is the newest
 version verified to work to build @theglibc{}.
 @end itemize
 
@@ -734,7 +734,7 @@ 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.18 is the newest stable version verified
+As of release time, Linux version 6.1.5 is the newest stable version verified
 to work to build @theglibc{}.
 
 @node Reporting Bugs

             reply	other threads:[~2023-02-01  1:12 UTC|newest]

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