diff options
Diffstat (limited to 'chapter05')
-rw-r--r-- | chapter05/chapter05.xml | 1 | ||||
-rw-r--r-- | chapter05/gcc-pass2.xml | 2 | ||||
-rw-r--r-- | chapter05/perl.xml | 8 |
3 files changed, 8 insertions, 3 deletions
diff --git a/chapter05/chapter05.xml b/chapter05/chapter05.xml index c4e45d336..a2734acc8 100644 --- a/chapter05/chapter05.xml +++ b/chapter05/chapter05.xml @@ -568,7 +568,6 @@ can now be used to build the rest of the temporary tools.</para> &c5-tar; &c5-texinfo; &c5-bash; -&c5-utillinux; &c5-perl; diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml index 982c267d6..462f92f0b 100644 --- a/chapter05/gcc-pass2.xml +++ b/chapter05/gcc-pass2.xml @@ -128,7 +128,7 @@ through to completion and not stop at the first failure. The GCC test suite is very comprehensive and is almost guaranteed to generate a few failures. To get a summary of the test suite results, run this:</para> -<screen><userinput>../&gcc-dir;/contrib/test_summary | more</userinput></screen> +<screen><userinput>../&gcc-dir;/contrib/test_summary | grep -A7 Summ</userinput></screen> <para>You can compare your results to those posted to the gcc-testresults mailing list for similar configurations to your own. For an example of how diff --git a/chapter05/perl.xml b/chapter05/perl.xml index dccb191c0..7251700c1 100644 --- a/chapter05/perl.xml +++ b/chapter05/perl.xml @@ -17,7 +17,13 @@ <screen><userinput>patch -Np1 -i ../&perl-libc-patch;</userinput></screen> -<para>Now prepare Perl for compilation (make sure to get the 'IO Fcntl' +<para>Perl insists on using the <command>arch</command> program to find out +the machine type. Create a little script to mimick this command:</para> + +<screen><userinput>echo "uname -m" > /tools/bin/arch +chmod 755 /tools/bin/arch</userinput></screen> + +<para>Now prepare Perl for compilation (make sure you get the 'IO Fcntl' right, they are all letters):</para> <screen><userinput>./configure.gnu --prefix=/tools -Dstatic_ext='IO Fcntl'</userinput></screen> |