diff options
Diffstat (limited to 'chapter05/gcc-pass2.xml')
| -rw-r--r-- | chapter05/gcc-pass2.xml | 21 |
1 files changed, 10 insertions, 11 deletions
diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml index 0e368c38a..4fe46290b 100644 --- a/chapter05/gcc-pass2.xml +++ b/chapter05/gcc-pass2.xml @@ -15,12 +15,12 @@ Estimated required disk space: &gcc-compsize-tools-pass2;</screen> <para>The tools required to test GCC and Binutils are installed now (Tcl, Expect and DejaGnu). We can continue on rebuilding GCC and Binutils, link them against -the new Glibc, and test them properly. One thing to note, however, is that these -test suites are highly dependent on properly functioning pseudo terminals (PTYs) -which are provided by your host distribution. These days, PTYs are most commonly -implemented via the <emphasis>devpts</emphasis> file system. You can quickly -check if your host system is set up correctly in this regard by performing a -simple test:</para> +the new Glibc, and test them properly (if performing the test suites in this +chapter). One thing to note, however, is that these test suites are highly +dependent on properly functioning pseudo terminals (PTYs) which are provided by +your host distribution. These days, PTYs are most commonly implemented via the +<emphasis>devpts</emphasis> file system. You can quickly check if your host +system is set up correctly in this regard by performing a simple test:</para> <screen><userinput>expect -c "spawn ls"</userinput></screen> @@ -116,11 +116,10 @@ needed to ensure that both C and C++ compilers are built.</para></listitem> as the compiler we're using to compile this GCC was built from the exact same version of the GCC sources we used earlier.</para> -<note><para>It's worth pointing out that running the GCC test suite here -is considered not as important as running it in -<xref linkend="chapter06"/>.</para></note> - -<para>Test the results:</para> +<para>Compilation is now complete. As discussed earlier, we don't recommend +running the test suites for the temporary tools here in this chapter. If you +still want to run the GCC test suite anyway, the following command will do +so:</para> <screen><userinput>make -k check</userinput></screen> |