1 files changed, 32 insertions, 37 deletions
diff --git a/manual/install.texi b/manual/install.texi
index f9cc190eba..df32b3952b 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -330,39 +330,6 @@ occurred.  You can specify @samp{stop-on-test-failure=y} when running
 @code{make check} to make the test run stop and exit with an error
 status immediately when a failure occurs.
 
-The @glibcadj{} pretty printers come with their own set of scripts for testing,
-which run together with the rest of the testsuite through @code{make check}.
-These scripts require the following tools to run successfully:
-
-@itemize @bullet
-@item
-Python 2.7/3.4 or later
-
-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. 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/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. As of release time GNU @code{debugger} 8.0.1 is the newest verified
-to work to test the pretty printers.
-@end itemize
-
-@noindent
-If these tools are absent, the printer tests will report themselves as
-@code{UNSUPPORTED}.  Notice that some of the printer tests require @theglibc{}
-to be compiled with debugging symbols.
-
 To format the @cite{GNU C Library Reference Manual} for printing, type
 @w{@code{make dvi}}.  You need a working @TeX{} installation to do
 this.  The distribution builds the on-line formatted version of the
@@ -577,10 +544,11 @@ verified to work to build @theglibc{}.
 @item
 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. As of release
-time @code{perl} version 5.28.0 is the newest verified to work to build
-@theglibc{}.
+Perl is not required, but if present it is used in some tests and the
+@code{mtrace} program, to build the @glibcadj{} manual, as well as to
+regenerate @file{locale/C-translit.h} if its source files are
+modified.  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
@@ -589,6 +557,33 @@ GNU @code{sed} 3.02 or newer
 with any version of @code{sed}.  As of release time, @code{sed} version
 4.5 is the newest verified to work to build @theglibc{}.
 
+@item
+Python 2.7/3.4 or later
+
+Python is required to run some tests.  As of release time, Python 3.6
+is the newest verified to work for testing @theglibc{}.
+
+@item PExpect 4.0
+
+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
+the pretty printers.
+
+@item
+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.  As of release time GNU @code{debugger}
+8.0.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
+that some of the printer tests require @theglibc{} to be compiled with
+debugging symbols.
 @end itemize
 
 @noindent