From: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
To: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>,
libc-alpha@sourceware.org
Subject: Re: [PATCHv3] Update INSTALL with package versions that are known to work
Date: Fri, 22 Jan 2021 15:15:47 -0300 [thread overview]
Message-ID: <8f0869f1-6144-75d9-83ee-c413392ec20c@linaro.org> (raw)
In-Reply-To: <20210122014321.1355869-1-tuliom@linux.ibm.com>
On 21/01/2021 22:43, Tulio Magno Quites Machado Filho wrote:
> Changes since v2:
> - Updated binutils, bison, gettext, perl, Python, PExpect and GDB.
>
> Changes since v1:
>
> - Incorporated a change that was in patch 1/2 by mistake
>
> ---8<---
>
> Most packages have been tested with their latest releases, except for
> Python, whose latest version is 3.9.1.
LGTM, thanks.
Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
> ---
> INSTALL | 26 +++++++++++++-------------
> manual/install.texi | 24 ++++++++++++------------
> 2 files changed, 25 insertions(+), 25 deletions(-)
>
> diff --git a/INSTALL b/INSTALL
> index f2e35da589..ed8156f93c 100644
> --- a/INSTALL
> +++ b/INSTALL
> @@ -460,15 +460,15 @@ build the GNU C Library:
>
> * GNU 'make' 4.0 or newer
>
> - As of relase time, GNU 'make' 4.2.1 is the newest verified to work
> - to build the GNU C Library.
> + As of relase time, GNU 'make' 4.3 is the newest verified to work to
> + build the GNU C Library.
>
Ok.
> * 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 the GNU C Library, as newer compilers usually produce
> - better code. As of release time, GCC 9.2.1 is the newest compiler
> + better code. As of release time, GCC 10.2 is the newest compiler
> verified to work to build the GNU C Library.
>
Ok.
> For PowerPC 64-bits little-endian (powerpc64le), a GCC version with
> @@ -503,7 +503,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.32 is the newest
> + moment. As of release time, GNU 'binutils' 2.35.1 is the newest
> verified to work to build the GNU C Library.
>
Ok.
> For PowerPC 64-bits little-endian (powerpc64le), 'as' is required
> @@ -519,7 +519,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.6 is the newest
> + differently. As of release time, 'texinfo' 6.7 is the newest
> verified to work to build the GNU C Library.
>
> * GNU 'awk' 3.1.2, or higher
Ok.
> @@ -527,32 +527,32 @@ 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.0.1 is the newest verified to work to build the GNU C
> + version 5.1 is the newest verified to work to build the GNU C
> Library.
>
Ok.
> * 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.4.1 is the
> + subdirectory. As of release time, 'bison' version 3.7.4 is the
> newest verified to work to build the GNU C Library.
>
Ok.
> * 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.30.1 is the newest verified to work
> + release time 'perl' version 5.32.0 is the newest verified to work
> to build the GNU C Library.
>
Ok.
> * GNU 'sed' 3.02 or newer
>
> 'Sed' is used in several places to generate files. Most scripts
> work with any version of 'sed'. As of release time, 'sed' version
> - 4.5 is the newest verified to work to build the GNU C Library.
> + 4.8 is the newest verified to work to 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.7.4 is the newest verified to work for building and
> + Python 3.8.6 is the newest verified to work for building and
> testing the GNU C Library.
>
> * PExpect 4.0
Ok.
> @@ -560,7 +560,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.3 is the newest
> + in your system. As of release time PExpect 4.8 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
> @@ -569,7 +569,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' 8.3 is the newest verified to work to test the
> + time GNU 'debugger' 10.1 is the newest verified to work to test the
> pretty printers.
>
> Unless Python, PExpect and GDB with Python support are present, the
Ok.
> @@ -585,7 +585,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.19.8.1 is the newest
> + As of release time, GNU 'gettext' version 0.21 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
Ok.
> diff --git a/manual/install.texi b/manual/install.texi
> index 77e219e3d0..8a865861f1 100644
> --- a/manual/install.texi
> +++ b/manual/install.texi
> @@ -497,7 +497,7 @@ build @theglibc{}:
> @item
> GNU @code{make} 4.0 or newer
>
> -As of relase time, GNU @code{make} 4.2.1 is the newest verified to work
> +As of relase time, GNU @code{make} 4.3 is the newest verified to work
> to build @theglibc{}.
>
> @item
Ok.
> @@ -506,7 +506,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 9.2.1 is the newest compiler verified to work to build
> +release time, GCC 10.2 is the newest compiler verified to work to build
> @theglibc{}.
>
Ok.
> For PowerPC 64-bits little-endian (powerpc64le), a GCC version with support
> @@ -542,7 +542,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.32 is the newest
> +moment. As of release time, GNU @code{binutils} 2.35.1 is the newest
> verified to work to build @theglibc{}.
>
> For PowerPC 64-bits little-endian (powerpc64le), @command{as} is required to
Ok.
> @@ -558,7 +558,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.6 is the newest verified to work
> +As of release time, @code{texinfo} 6.7 is the newest verified to work
> to build @theglibc{}.
>
> @item
> @@ -567,14 +567,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.0.1 is the newest verified
> +As of release time, @code{gawk} version 5.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.4.1 is the newest
> +subdirectory. As of release time, @code{bison} version 3.7.4 is the newest
> verified to work to build @theglibc{}.
>
> @item
Ok.
> @@ -582,7 +582,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.30.1 is the newest verified to work to
> +time @code{perl} version 5.32.0 is the newest verified to work to
> build @theglibc{}.
>
> @item
> @@ -590,13 +590,13 @@ GNU @code{sed} 3.02 or newer
>
> @code{Sed} is used in several places to generate files. Most scripts work
> with any version of @code{sed}. As of release time, @code{sed} version
> -4.5 is the newest verified to work to build @theglibc{}.
> +4.8 is the newest verified to work to build @theglibc{}.
>
> @item
> Python 3.4 or later
>
> Python is required to build @theglibc{}. As of release time, Python
> -3.7.4 is the newest verified to work for building and testing
> +3.8.6 is the newest verified to work for building and testing
> @theglibc{}.
>
> @item PExpect 4.0
Ok.
> @@ -604,7 +604,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.3 is the newest verified to work to test
> +As of release time PExpect 4.8 is the newest verified to work to test
> the pretty printers.
>
> @item
> @@ -614,7 +614,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}
> -8.3 is the newest verified to work to test the pretty printers.
> +10.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
> @@ -637,7 +637,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.19.8.1 is the newest
> +As of release time, GNU @code{gettext} version 0.21 is the newest
> version verified to work to build @theglibc{}.
> @end itemize
>
>
Ok.
next prev parent reply other threads:[~2021-01-22 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 1:43 [PATCHv3] Update INSTALL with package versions that are known to work Tulio Magno Quites Machado Filho via Libc-alpha
2021-01-22 18:15 ` Adhemerval Zanella via Libc-alpha [this message]
2021-01-25 16:15 ` Tulio Magno Quites Machado Filho via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f0869f1-6144-75d9-83ee-c413392ec20c@linaro.org \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=tuliom@linux.ibm.com \
/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).