diff options
| author | Greg Schafer <greg@linuxfromscratch.org> | 2003-10-09 23:22:07 +0000 |
|---|---|---|
| committer | Greg Schafer <greg@linuxfromscratch.org> | 2003-10-09 23:22:07 +0000 |
| commit | 21ba4e3570c1c2524b0733d492ced9634b259353 (patch) | |
| tree | f5124d2e6106d2e29e5b32f79b56a90defabdbd9 /chapter05/gcc-pass2-inst.xml | |
| parent | 1a7aecc6119f540e24a4e8da1b583a625b5690c1 (diff) | |
Internal markup reworking to fix the extraneous whitespace problem in the "tidy generated" web site pages. Essentially replace all ocurrences of <para><screen> with <screen> (and of course the matching closing tags).
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2958 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/gcc-pass2-inst.xml')
| -rw-r--r-- | chapter05/gcc-pass2-inst.xml | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/chapter05/gcc-pass2-inst.xml b/chapter05/gcc-pass2-inst.xml index e2e58ab19..65a2964c7 100644 --- a/chapter05/gcc-pass2-inst.xml +++ b/chapter05/gcc-pass2-inst.xml @@ -12,7 +12,7 @@ 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> -<para><screen><userinput>expect -c "spawn ls"</userinput></screen></para> +<screen><userinput>expect -c "spawn ls"</userinput></screen> <para>If you receive the message:</para> @@ -33,8 +33,8 @@ same working directory. They will all unfold into a single <para>First correct one problem and make an essential adjustment:</para> -<para><screen><userinput>patch -Np1 -i ../&gcc-nofixincludes-patch; -patch -Np1 -i ../&gcc-specs-patch;</userinput></screen></para> +<screen><userinput>patch -Np1 -i ../&gcc-nofixincludes-patch; +patch -Np1 -i ../&gcc-specs-patch;</userinput></screen> <para>The first patch disables the GCC "fixincludes" script. We mentioned this briefly earlier, but a slightly more in-depth explanation of the fixincludes @@ -60,19 +60,19 @@ successful overall build. Do not forget to apply them.</para></important> <para>Create a separate build directory again:</para> -<para><screen><userinput>mkdir ../gcc-build -cd ../gcc-build</userinput></screen></para> +<screen><userinput>mkdir ../gcc-build +cd ../gcc-build</userinput></screen> <para>Before starting to build GCC, remember to unset any environment variables that override the default optimization flags.</para> <para>Now prepare GCC to be compiled:</para> -<para><screen><userinput>../gcc-&gcc-version;/configure --prefix=/tools \ +<screen><userinput>../gcc-&gcc-version;/configure --prefix=/tools \ --with-local-prefix=/tools \ --enable-clocale=gnu --enable-shared \ --enable-threads=posix --enable-__cxa_atexit \ - --enable-languages=c,c++</userinput></screen></para> + --enable-languages=c,c++</userinput></screen> <para>The meaning of the new configure options:</para> @@ -101,7 +101,7 @@ needed to ensure that both C and C++ compilers are built.</para></listitem> <para>Compile the package:</para> -<para><screen><userinput>make</userinput></screen></para> +<screen><userinput>make</userinput></screen> <para>There is no need to use the <userinput>bootstrap</userinput> target now, as the compiler we're using to compile this GCC was built from the exact same @@ -109,14 +109,14 @@ version of the GCC sources we used earlier.</para> <para>Test the results:</para> -<para><screen><userinput>make -k check</userinput></screen></para> +<screen><userinput>make -k check</userinput></screen> <para>The <userinput>-k</userinput> flag is used to make the test suite run 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> -<para><screen><userinput>../gcc-&gcc-version;/contrib/test_summary | less</userinput></screen></para> +<screen><userinput>../gcc-&gcc-version;/contrib/test_summary | less</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 @@ -150,7 +150,7 @@ to continue on.</para> <para>And finally install the package:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> <note><para>At this point it is strongly recommended to repeat the sanity check we performed earlier in the chapter. Refer back to |