public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Andreas K. Huttel <dilfridge@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] install.texi: Update versions of most recent build tools Date: Thu, 27 Jul 2023 21:01:41 +0000 (GMT) [thread overview] Message-ID: <20230727210142.012393858C36@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=14126ff059e98e9236633741fd323a1116299872 commit 14126ff059e98e9236633741fd323a1116299872 Author: Andreas K. Hüttel <dilfridge@gentoo.org> Date: Thu Jul 27 23:00:59 2023 +0200 install.texi: Update versions of most recent build tools Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org> Diff: --- manual/install.texi | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/manual/install.texi b/manual/install.texi index 623d64a4b5..51605b4fbf 100644 --- a/manual/install.texi +++ b/manual/install.texi @@ -528,7 +528,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 13.0 is the newest compiler verified to work to build +release time, GCC 13.2 is the newest compiler verified to work to build @theglibc{}. For PowerPC 64-bits little-endian (powerpc64le), a GCC version with support @@ -567,7 +567,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.39 is the newest +moment. As of release time, GNU @code{binutils} 2.40 is the newest verified to work to build @theglibc{}. For PowerPC 64-bits little-endian (powerpc64le), @command{objcopy} is required @@ -583,7 +583,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} 7.0.2 is the newest verified to work +As of release time, @code{texinfo} 7.0.3 is the newest verified to work to build @theglibc{}. @item @@ -592,7 +592,7 @@ 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.1 is the newest verified +As of release time, @code{gawk} version 5.2.2 is the newest verified to work to build @theglibc{}. @item @@ -607,7 +607,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.36.0 is the newest verified to work to +time @code{perl} version 5.38.0 is the newest verified to work to build @theglibc{}. @item @@ -615,7 +615,7 @@ 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.8 is the newest verified to work to build @theglibc{}. +4.9 is the newest verified to work to build @theglibc{}. @item Python 3.4 or later @@ -639,7 +639,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} -12.1 is the newest verified to work to test the pretty printers. +13.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
reply other threads:[~2023-07-27 21:01 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230727210142.012393858C36@sourceware.org \ --to=dilfridge@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).