diff options
-rw-r--r-- | chapter01/changelog.xml | 6 | ||||
-rw-r--r-- | chapter06/binutils.xml | 15 |
2 files changed, 14 insertions, 7 deletions
diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml index 1498f1454..815b83e5d 100644 --- a/chapter01/changelog.xml +++ b/chapter01/changelog.xml @@ -41,6 +41,12 @@ <para>2009-03-12</para> <itemizedlist> <listitem> + <para>[matthew] - Reword the explanation of the Expect tests in Binutils' + instructions to clarify what the expected test output is. Thanks to Chris + Staub for the report and patch. Fixes + <ulink url="&lfs-ticket-root;2365">#2365</ulink>.</para> + </listitem> + <listitem> <para>[matthew] - Reorder the contents of chapter 7 to flow better. Thanks to Chris Staub for the report and suggested order. Fixes <ulink url="&lfs-ticket-root;2366">#2366</ulink>.</para> diff --git a/chapter06/binutils.xml b/chapter06/binutils.xml index 3f3fed95f..19e693415 100644 --- a/chapter06/binutils.xml +++ b/chapter06/binutils.xml @@ -42,20 +42,21 @@ <title>Installation of Binutils</title> <para>Verify that the PTYs are working properly inside the chroot - environment. Check that everything is set up correctly by performing a - simple test:</para> + environment by performing a simple test:</para> <screen><userinput remap="test">expect -c "spawn ls"</userinput></screen> - <para>If the following message shows up, the chroot environment is not - set up for proper PTY operation:</para> + <para>This command should output the following:</para> + +<screen><computeroutput>spawn ls</computeroutput></screen> + + <para>If, instead, the output includes the message below, then the environment + is not set up for proper PTY operation. This issue needs to be resolved before + running the test suites for Binutils and GCC:</para> <screen><computeroutput>The system has no more ptys. Ask your system administrator to create more.</computeroutput></screen> - <para>This issue needs to be resolved before running the test suites - for Binutils and GCC.</para> - <para>Suppress the installation of an outdated <filename>standards.info</filename> file as a newer one is installed later on in the Autoconf instructions:</para> |