* glibc 2.28 status --- Most recent gcc and binutils used?
@ 2018-07-28 0:20 Carlos O'Donell
2018-07-28 1:34 ` Tulio Magno Quites Machado Filho
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Carlos O'Donell @ 2018-07-28 0:20 UTC (permalink / raw)
To: GNU C Library
Community,
I'm updating manual/install.texi.
We currently list the following versions of tools as recently tested:
General:
* gmake 4.0
* gcc (no specific newest tested version listed)
* binutils 2.29.1
* texinfo 6.5
* gawk 4.2.0
* bison 3.0.4
* perl 5
* sed 4.4
Pretty printers:
* python 2.7.6, or 3.4.3
* PExpect 4.0
* gdb 7.8
If you have used a version of these tools that is newer than on this
list, please tell me which version, and if your build worked, such
that I can update the expected versions to work list.
I'd really like to get GCC updated to list a specific newest version
that works to compile glibc, likewise with binutils.
Thank you!
Cheers,
Carlos.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: glibc 2.28 status --- Most recent gcc and binutils used?
2018-07-28 0:20 glibc 2.28 status --- Most recent gcc and binutils used? Carlos O'Donell
@ 2018-07-28 1:34 ` Tulio Magno Quites Machado Filho
2018-07-30 13:59 ` Joseph Myers
2018-07-31 18:53 ` Dmitry V. Levin
2018-07-31 20:39 ` Carlos O'Donell
2 siblings, 1 reply; 6+ messages in thread
From: Tulio Magno Quites Machado Filho @ 2018-07-28 1:34 UTC (permalink / raw)
To: Carlos O'Donell, GNU C Library
Carlos O'Donell <carlos@redhat.com> writes:
> If you have used a version of these tools that is newer than on this
> list, please tell me which version, and if your build worked, such
> that I can update the expected versions to work list.
I've also tested with:
> General:
> * gmake 4.0
gmake 4.2.1
> * gcc (no specific newest tested version listed)
gcc 8.1
> * binutils 2.29.1
Binutils 2.30.0
> * gawk 4.2.0
gawk 4.2.1
> Pretty printers:
> * python 2.7.6, or 3.4.3
Python 3.6.5
> * PExpect 4.0
PExpect 4.5.0
> * gdb 7.8
GDB 8.1
--
Tulio Magno
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: glibc 2.28 status --- Most recent gcc and binutils used?
2018-07-28 1:34 ` Tulio Magno Quites Machado Filho
@ 2018-07-30 13:59 ` Joseph Myers
2018-07-30 15:10 ` Carlos O'Donell
0 siblings, 1 reply; 6+ messages in thread
From: Joseph Myers @ 2018-07-30 13:59 UTC (permalink / raw)
To: Tulio Magno Quites Machado Filho; +Cc: Carlos O'Donell, GNU C Library
On Fri, 27 Jul 2018, Tulio Magno Quites Machado Filho wrote:
> > Pretty printers:
> > * python 2.7.6, or 3.4.3
>
> Python 3.6.5
I'm not actually clear on why we list those particular minor versions as
required rather than just 2.7 / 3.4. If the intent is to support any
non-EOL Python version that means 2.7 or 3.4 or later (see the table of
branch status on <https://devguide.python.org/>), but that doesn't mean
anything in particular about minor versions (in that a distribution might
backport selected release branch fixes without increasing the version
number).
--
Joseph S. Myers
joseph@codesourcery.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: glibc 2.28 status --- Most recent gcc and binutils used?
2018-07-30 13:59 ` Joseph Myers
@ 2018-07-30 15:10 ` Carlos O'Donell
0 siblings, 0 replies; 6+ messages in thread
From: Carlos O'Donell @ 2018-07-30 15:10 UTC (permalink / raw)
To: Joseph Myers, Tulio Magno Quites Machado Filho; +Cc: GNU C Library
On 07/30/2018 09:59 AM, Joseph Myers wrote:
> On Fri, 27 Jul 2018, Tulio Magno Quites Machado Filho wrote:
>
>>> Pretty printers:
>>> * python 2.7.6, or 3.4.3
>>
>> Python 3.6.5
>
> I'm not actually clear on why we list those particular minor versions as
> required rather than just 2.7 / 3.4. If the intent is to support any
> non-EOL Python version that means 2.7 or 3.4 or later (see the table of
> branch status on <https://devguide.python.org/>), but that doesn't mean
> anything in particular about minor versions (in that a distribution might
> backport selected release branch fixes without increasing the version
> number).
I think that they are simply over-specified. I'm going to clean this up to
be 2.7 and 3.4. But I will list the most recently used version that works.
--
Cheers,
Carlos.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: glibc 2.28 status --- Most recent gcc and binutils used?
2018-07-28 0:20 glibc 2.28 status --- Most recent gcc and binutils used? Carlos O'Donell
2018-07-28 1:34 ` Tulio Magno Quites Machado Filho
@ 2018-07-31 18:53 ` Dmitry V. Levin
2018-07-31 20:39 ` Carlos O'Donell
2 siblings, 0 replies; 6+ messages in thread
From: Dmitry V. Levin @ 2018-07-31 18:53 UTC (permalink / raw)
To: libc-alpha
On Fri, Jul 27, 2018 at 08:20:12PM -0400, Carlos O'Donell wrote:
> Community,
>
> I'm updating manual/install.texi.
>
> We currently list the following versions of tools as recently tested:
>
> General:
> * gmake 4.0
> * gcc (no specific newest tested version listed)
I'm quite sure the newest tested version of gcc was listed for glibc 2.27
by commit glibc-2.27~9 and corrected by commit glibc-2.27~8.
Yes, it needs to be updated for glibc 2.28, but it is listed. :)
--
ldv
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: glibc 2.28 status --- Most recent gcc and binutils used?
2018-07-28 0:20 glibc 2.28 status --- Most recent gcc and binutils used? Carlos O'Donell
2018-07-28 1:34 ` Tulio Magno Quites Machado Filho
2018-07-31 18:53 ` Dmitry V. Levin
@ 2018-07-31 20:39 ` Carlos O'Donell
2 siblings, 0 replies; 6+ messages in thread
From: Carlos O'Donell @ 2018-07-31 20:39 UTC (permalink / raw)
To: GNU C Library
[-- Attachment #1: Type: text/plain, Size: 868 bytes --]
On 07/27/2018 08:20 PM, Carlos O'Donell wrote:
> Community,
>
> I'm updating manual/install.texi.
>
> We currently list the following versions of tools as recently tested:
>
> General:
> * gmake 4.0
> * gcc (no specific newest tested version listed)
> * binutils 2.29.1
> * texinfo 6.5
> * gawk 4.2.0
> * bison 3.0.4
> * perl 5
> * sed 4.4
>
> Pretty printers:
> * python 2.7.6, or 3.4.3
> * PExpect 4.0
> * gdb 7.8
>
> If you have used a version of these tools that is newer than on this
> list, please tell me which version, and if your build worked, such
> that I can update the expected versions to work list.
>
> I'd really like to get GCC updated to list a specific newest version
> that works to compile glibc, likewise with binutils.
I'm going to check this patch in with updated versions based on my
own testing in Fedora Rawhide.
--
Cheers,
Carlos.
[-- Attachment #2: 0001-Update-tooling-versions-verified-to-work-with-glibc.patch --]
[-- Type: text/x-patch, Size: 8988 bytes --]
From f650932b34f23b94a49b245405db65c3b00bd0ed Mon Sep 17 00:00:00 2001
From: Carlos O'Donell <carlos@redhat.com>
Date: Tue, 31 Jul 2018 16:37:07 -0400
Subject: [PATCH] Update tooling versions verified to work with glibc.
---
ChangeLog | 3 +++
INSTALL | 33 +++++++++++++++++++++++----------
manual/install.texi | 31 +++++++++++++++++++++----------
3 files changed, 47 insertions(+), 20 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index dc409ae17d..5e78ad8ce1 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,8 @@
2018-07-31 Carlos O'Donell <carlos@redhat.com>
+ * manual/install.texi: Update versions.
+ * INSTALL: Regenerate.
+
* manual/contrib.texi (Contributors): Update contributions.
2018-07-31 Carlos O'Donell <carlos@redhat.com>
diff --git a/INSTALL b/INSTALL
index 840b862511..781cb8415b 100644
--- a/INSTALL
+++ b/INSTALL
@@ -301,23 +301,28 @@ for testing, which run together with the rest of the testsuite through
'make check'. These scripts require the following tools to run
successfully:
- * Python 2.7.6/3.4.3 or later
+ * Python 2.7/3.4 or later
- Python is required for running the printers' test scripts.
+ Python is required for running the printers' test scripts. As of
+ release time, Python 3.6 is the newest verified to work to test the
+ pretty printers.
* PExpect 4.0
The 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.
+ system. As of release time PExpect 4.3 is the newest verified to
+ work to test the pretty printers.
- * GDB 7.8 or later with support for Python 2.7.6/3.4.3 or later
+ * GDB 7.8 or later with support for Python 2.7/3.4 or later
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.
+ system's Python and GDB's have the same version. As of release
+ time GNU 'debugger' 8.0.1 is the newest verified to work to test
+ the pretty printers.
If these tools are absent, the printer tests will report themselves as
'UNSUPPORTED'. Notice that some of the printer tests require the GNU C
@@ -444,12 +449,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.
+
* GCC 4.9 or newer
GCC 4.9 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 7.3 is the newest compiler
+ better code. As of release time, GCC 8.1.1 is the newest compiler
verified to work to build the GNU C Library.
For PowerPC 64-bits little-endian (powerpc64le), GCC 6.2 or higher
@@ -476,7 +484,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.29.1 is the newest
+ moment. As of release time, GNU 'binutils' 2.31.1 is the newest
verified to work to build the GNU C Library.
* GNU 'texinfo' 4.7 or later
@@ -493,7 +501,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 4.2.0 is the newest verified to work to build the GNU C
+ version 4.2.1 is the newest verified to work to build the GNU C
Library.
* GNU 'bison' 2.7 or later
@@ -505,13 +513,15 @@ build the GNU C Library:
* Perl 5
Perl is not required, but it is used if present to test the
- installation. We may decide to use it elsewhere in the future.
+ installation. We may decide to use it elsewhere in the future. As
+ of release time 'perl' version 5.28.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.4 is the newest verified to work to build the GNU C Library.
+ 4.5 is the newest verified to work to build the GNU C Library.
If you change any of the 'configure.ac' files you will also need
@@ -521,6 +531,9 @@ 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
+ version verified to work to build the GNU C Library.
+
You may also need these packages if you upgrade your source tree using
patches, although we try to avoid this.
diff --git a/manual/install.texi b/manual/install.texi
index a8577dd610..c39e63bf3b 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -336,23 +336,26 @@ These scripts require the following tools to run successfully:
@itemize @bullet
@item
-Python 2.7.6/3.4.3 or later
+Python 2.7/3.4 or later
-Python is required for running the printers' test scripts.
+Python is required for running the printers' test scripts. As of release time,
+Python 3.6 is the newest verified to work to test the pretty printers.
@item PExpect 4.0
The 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.
+compatible with the Python version in your system. As of release time
+PExpect 4.3 is the newest verified to work to test the pretty printers.
@item
-GDB 7.8 or later with support for Python 2.7.6/3.4.3 or later
+GDB 7.8 or later with support for Python 2.7/3.4 or later
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.
+version. As of release time GNU @code{debugger} 8.0.1 is the newest verified
+to work to test the pretty printers.
@end itemize
@noindent
@@ -491,13 +494,16 @@ 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
+to build @theglibc{}.
+
@item
GCC 4.9 or newer
GCC 4.9 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 7.3 is the newest compiler verified to work to build
+release time, GCC 8.1.1 is the newest compiler verified to work to build
@theglibc{}.
For PowerPC 64-bits little-endian (powerpc64le), GCC 6.2 or higher is
@@ -522,7 +528,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.29.1 is the newest
+moment. As of release time, GNU @code{binutils} 2.31.1 is the newest
verified to work to build @theglibc{}.
@item
@@ -541,7 +547,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 4.2.0 is the newest verified
+As of release time, @code{gawk} version 4.2.1 is the newest verified
to work to build @theglibc{}.
@item
@@ -555,14 +561,16 @@ verified to work to build @theglibc{}.
Perl 5
Perl is not required, but it is used if present to test the
-installation. We may decide to use it elsewhere in the future.
+installation. We may decide to use it elsewhere in the future. As of release
+time @code{perl} version 5.28.0 is the newest verified to work to build
+@theglibc{}.
@item
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.4 is the newest verified to work to build @theglibc{}.
+4.5 is the newest verified to work to build @theglibc{}.
@end itemize
@@ -580,6 +588,9 @@ and if you change any of the message translation files you will need
@itemize @bullet
@item
GNU @code{gettext} 0.10.36 or later
+
+As of release time, GNU @code{gettext} version 0.19.8.1 is the newest
+version verified to work to build @theglibc{}.
@end itemize
--
2.14.4
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2018-07-31 20:39 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-07-28 0:20 glibc 2.28 status --- Most recent gcc and binutils used? Carlos O'Donell
2018-07-28 1:34 ` Tulio Magno Quites Machado Filho
2018-07-30 13:59 ` Joseph Myers
2018-07-30 15:10 ` Carlos O'Donell
2018-07-31 18:53 ` Dmitry V. Levin
2018-07-31 20:39 ` Carlos O'Donell
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).