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: regenerate Date: Sun, 30 Jul 2023 19:19:44 +0000 (GMT) [thread overview] Message-ID: <20230730191944.3F0683858D35@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=d09871da52b0eebbe4681660b25febfe1dc54cd9 commit d09871da52b0eebbe4681660b25febfe1dc54cd9 Author: Andreas K. Hüttel <dilfridge@gentoo.org> Date: Sun Jul 30 21:16:02 2023 +0200 INSTALL: regenerate Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org> Diff: --- INSTALL | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/INSTALL b/INSTALL index da24b95c97..268acadd75 100644 --- a/INSTALL +++ b/INSTALL @@ -487,7 +487,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 13.0 is the newest compiler + better code. As of release time, GCC 13.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 @@ -525,7 +525,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.39 is the newest + moment. As of release time, GNU ‘binutils’ 2.41 is the newest verified to work to build the GNU C Library. For PowerPC 64-bits little-endian (powerpc64le), ‘objcopy’ is @@ -541,7 +541,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’ 7.0.2 is the newest + differently. As of release time, ‘texinfo’ 7.0.3 is the newest verified to work to build the GNU C Library. • GNU ‘awk’ 3.1.2, or higher @@ -549,7 +549,7 @@ 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.1 is the newest verified to work to build the GNU C + version 5.2.2 is the newest verified to work to build the GNU C Library. • GNU ‘bison’ 2.7 or later @@ -562,14 +562,14 @@ 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.36.0 is the newest verified to work + release time ‘perl’ version 5.38.0 is the newest verified to work to build the GNU C Library. • 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.8 is the newest verified to work to build the GNU C Library. + 4.9 is the newest verified to work to build the GNU C Library. • Python 3.4 or later @@ -591,7 +591,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’ 12.1 is the newest verified to work to test the + time GNU ‘debugger’ 13.2 is the newest verified to work to test the pretty printers. Unless Python, PExpect and GDB with Python support are present, the
next reply other threads:[~2023-07-30 19:19 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-30 19:19 Andreas K. Huttel [this message] 2024-01-09 13:56 Mark Wielaard
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=20230730191944.3F0683858D35@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).