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 | |
| 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')
32 files changed, 161 insertions, 161 deletions
diff --git a/chapter05/adding-user.xml b/chapter05/adding-user.xml index d8dd85422..65aaa8a2d 100644 --- a/chapter05/adding-user.xml +++ b/chapter05/adding-user.xml @@ -10,20 +10,20 @@ work environment we'll create a new user <emphasis>lfs</emphasis> and use this one during the installation process. As <emphasis>root</emphasis>, issue the following commands to add the new user:</para> -<para><screen><userinput>useradd -s /bin/bash -m lfs -passwd lfs</userinput></screen></para> +<screen><userinput>useradd -s /bin/bash -m lfs +passwd lfs</userinput></screen> <para>Now grant this new user <emphasis>lfs</emphasis> full access to <filename class="directory">$LFS/tools</filename> by giving it ownership of the directory:</para> -<para><screen><userinput>chown lfs $LFS/tools</userinput></screen></para> +<screen><userinput>chown lfs $LFS/tools</userinput></screen> <para>Next, login as user <emphasis>lfs</emphasis>. This can be done via a virtual console, through a display manager, or with the following substitute user command:</para> -<para><screen><userinput>su - lfs</userinput></screen></para> +<screen><userinput>su - lfs</userinput></screen> <para>The "<userinput>-</userinput>" instructs <userinput>su</userinput> to start a new, clean shell.</para> diff --git a/chapter05/bash-inst.xml b/chapter05/bash-inst.xml index 03fe846ae..0a3a96933 100644 --- a/chapter05/bash-inst.xml +++ b/chapter05/bash-inst.xml @@ -6,30 +6,30 @@ <para>Bash contains several known bugs. Fix these with the following patch:</para> -<para><screen><userinput>patch -Np1 -i ../&bash-patch;</userinput></screen></para> +<screen><userinput>patch -Np1 -i ../&bash-patch;</userinput></screen> <para>Now prepare Bash for compilation:</para> -<para><screen><userinput>./configure --prefix=/tools</userinput></screen></para> +<screen><userinput>./configure --prefix=/tools</userinput></screen> <para>Compile the program:</para> -<para><screen><userinput>make</userinput></screen></para> +<screen><userinput>make</userinput></screen> <para>This package has a test suite available which can perform a number of checks to ensure it built correctly. Should you choose to run it, the following command will do so:</para> -<para><screen><userinput>make tests</userinput></screen></para> +<screen><userinput>make tests</userinput></screen> <para>Then install it and its documentation:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> <para>And make a link for the programs that use <userinput>sh</userinput> for a shell:</para> -<para><screen><userinput>ln -s bash /tools/bin/sh</userinput></screen></para> +<screen><userinput>ln -s bash /tools/bin/sh</userinput></screen> </sect2> diff --git a/chapter05/binutils-pass1-inst.xml b/chapter05/binutils-pass1-inst.xml index c4d1dc052..3ee78e841 100644 --- a/chapter05/binutils-pass1-inst.xml +++ b/chapter05/binutils-pass1-inst.xml @@ -21,13 +21,13 @@ modifying them when building Binutils.</para> <para>The Binutils documentation recommends building Binutils outside of the source directory in a dedicated build directory:</para> -<para><screen><userinput>mkdir ../binutils-build -cd ../binutils-build</userinput></screen></para> +<screen><userinput>mkdir ../binutils-build +cd ../binutils-build</userinput></screen> <para>Next, prepare Binutils to be compiled:</para> -<para><screen><userinput>../binutils-&binutils-version;/configure \ - --prefix=/tools --disable-nls</userinput></screen></para> +<screen><userinput>../binutils-&binutils-version;/configure \ + --prefix=/tools --disable-nls</userinput></screen> <para>The meaning of the configure options:</para> @@ -44,8 +44,8 @@ when linking statically.</para></listitem> <para>Continue with compiling the package:</para> -<para><screen><userinput>make configure-host -make LDFLAGS="-all-static"</userinput></screen></para> +<screen><userinput>make configure-host +make LDFLAGS="-all-static"</userinput></screen> <para>The meaning of the make option:</para> @@ -59,12 +59,12 @@ strictly speaking, <userinput>"-all-static"</userinput> is first passed to the <para>And install the package:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> <para>Now prepare the linker for the "locking in" of Glibc later on:</para> -<para><screen><userinput>make -C ld clean -make -C ld LDFLAGS="-all-static" LIB_PATH=/tools/lib</userinput></screen></para> +<screen><userinput>make -C ld clean +make -C ld LDFLAGS="-all-static" LIB_PATH=/tools/lib</userinput></screen> <para>The meaning of the make options:</para> diff --git a/chapter05/binutils-pass2-inst.xml b/chapter05/binutils-pass2-inst.xml index 7b46d7ce8..901f89ed1 100644 --- a/chapter05/binutils-pass2-inst.xml +++ b/chapter05/binutils-pass2-inst.xml @@ -9,13 +9,13 @@ section is considered not as important as the one we run in Chapter 6.</para> <para>Create a separate build directory again:</para> -<para><screen><userinput>mkdir ../binutils-build -cd ../binutils-build</userinput></screen></para> +<screen><userinput>mkdir ../binutils-build +cd ../binutils-build</userinput></screen> <para>Now prepare Binutils to be compiled:</para> -<para><screen><userinput>../binutils-&binutils-version;/configure --prefix=/tools \ - --enable-shared --with-lib-path=/tools/lib</userinput></screen></para> +<screen><userinput>../binutils-&binutils-version;/configure --prefix=/tools \ + --enable-shared --with-lib-path=/tools/lib</userinput></screen> <para>The meaning of the new configure option:</para> @@ -31,12 +31,12 @@ variables that override the default optimization flags.</para> <para>Compile the package:</para> -<para><screen><userinput>make </userinput></screen></para> +<screen><userinput>make </userinput></screen> <para>Test the results (there should be no unexpected failures here, expected failures are fine):</para> -<para><screen><userinput>make check</userinput></screen></para> +<screen><userinput>make check</userinput></screen> <para>Unfortunately, there is no easy way to view the test results summary like there was for the previous GCC package. However, if a failure occurs here, it @@ -46,13 +46,13 @@ should be easy to spot. The output shown will contain something like:</para> <para>And install the package:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> <para>Now prepare Binutils for the re-adjusting of the toolchain in the next chapter:</para> -<para><screen><userinput>make -C ld clean -make -C ld LIB_PATH=/usr/lib:/lib</userinput></screen></para> +<screen><userinput>make -C ld clean +make -C ld LIB_PATH=/usr/lib:/lib</userinput></screen> <warning><para>Do not yet remove the Binutils source and build directories. We'll need these directories again in the next chapter in the state they are in diff --git a/chapter05/bzip2-inst.xml b/chapter05/bzip2-inst.xml index ad250d87b..0cce861b1 100644 --- a/chapter05/bzip2-inst.xml +++ b/chapter05/bzip2-inst.xml @@ -6,7 +6,7 @@ <para>The Bzip2 package doesn't contain a <userinput>configure</userinput> script. Compile and install it with a straightforward:</para> -<para><screen><userinput>make PREFIX=/tools install</userinput></screen></para> +<screen><userinput>make PREFIX=/tools install</userinput></screen> </sect2> diff --git a/chapter05/chapter05.xml b/chapter05/chapter05.xml index 4f1bc31b1..d5dfc685c 100644 --- a/chapter05/chapter05.xml +++ b/chapter05/chapter05.xml @@ -45,8 +45,8 @@ small, you will be glad to learn that you can throw away some unnecessary things. The executables and libraries you have built so far contain about 130 MB of unneeded debugging symbols. Remove those symbols like this:</para> -<para><screen><userinput>strip --strip-unneeded /tools/{,s}bin/* -strip --strip-debug /tools/lib/*</userinput></screen></para> +<screen><userinput>strip --strip-unneeded /tools/{,s}bin/* +strip --strip-debug /tools/lib/*</userinput></screen> <para>The first of the above commands will skip some twenty files, reporting that it doesn't recognize their file format. Most of them are scripts instead @@ -59,7 +59,7 @@ destroyed and you would have to build Glibc all over again.</para> <para>To save another couple of megabytes, you can throw away all the documentation:</para> -<para><screen><userinput>rm -rf /tools/{,share/}{doc,info,man}</userinput></screen></para> +<screen><userinput>rm -rf /tools/{,share/}{doc,info,man}</userinput></screen> <para>You will now need to have at least 700 MB of free space on your LFS filesystem to be able to build and install Glibc in the next phase.</para> diff --git a/chapter05/coreutils-inst.xml b/chapter05/coreutils-inst.xml index 90dbbd235..4d58b1cc4 100644 --- a/chapter05/coreutils-inst.xml +++ b/chapter05/coreutils-inst.xml @@ -5,17 +5,17 @@ <para>Prepare Coreutils to be compiled:</para> -<para><screen><userinput>./configure --prefix=/tools</userinput></screen></para> +<screen><userinput>./configure --prefix=/tools</userinput></screen> <para>Compile the package:</para> -<para><screen><userinput>make</userinput></screen></para> +<screen><userinput>make</userinput></screen> <para>This package has a test suite available which can perform a number of checks to ensure it built correctly. Should you choose to run it, the following command will do so:</para> -<para><screen><userinput>make RUN_EXPENSIVE_TESTS=yes check</userinput></screen></para> +<screen><userinput>make RUN_EXPENSIVE_TESTS=yes check</userinput></screen> <para>The meaning of the make option:</para> @@ -28,7 +28,7 @@ Linux.</para></listitem> <para>And install the package:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> </sect2> diff --git a/chapter05/creatingstage1dir.xml b/chapter05/creatingstage1dir.xml index 2ef07c1a6..2621ec6b3 100644 --- a/chapter05/creatingstage1dir.xml +++ b/chapter05/creatingstage1dir.xml @@ -15,13 +15,13 @@ use something like "tools-for-lfs".</para> <para>Create the required directory by running the following:</para> -<para><screen><userinput>mkdir $LFS/tools</userinput></screen></para> +<screen><userinput>mkdir $LFS/tools</userinput></screen> <para>The next step is to create a <filename>/tools</filename> symlink on your host system. It will point to the directory we just created on the LFS partition:</para> -<para><screen><userinput>ln -s $LFS/tools /</userinput></screen></para> +<screen><userinput>ln -s $LFS/tools /</userinput></screen> <para>This symlink enables us to compile our toolchain so that it always refers to <filename>/tools</filename>, meaning that the compiler, assembler diff --git a/chapter05/dejagnu-inst.xml b/chapter05/dejagnu-inst.xml index e9a172670..6f6256b8c 100644 --- a/chapter05/dejagnu-inst.xml +++ b/chapter05/dejagnu-inst.xml @@ -5,11 +5,11 @@ <para>Prepare DejaGnu to be compiled:</para> -<para><screen><userinput>./configure --prefix=/tools</userinput></screen></para> +<screen><userinput>./configure --prefix=/tools</userinput></screen> <para>Build and install the package:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> </sect2> diff --git a/chapter05/diffutils-inst.xml b/chapter05/diffutils-inst.xml index 2005334d8..4f8048c13 100644 --- a/chapter05/diffutils-inst.xml +++ b/chapter05/diffutils-inst.xml @@ -5,15 +5,15 @@ <para>Prepare Diffutils to be compiled:</para> -<para><screen><userinput>./configure --prefix=/tools</userinput></screen></para> +<screen><userinput>./configure --prefix=/tools</userinput></screen> <para>Compile the package:</para> -<para><screen><userinput>make</userinput></screen></para> +<screen><userinput>make</userinput></screen> <para>And install it:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> </sect2> diff --git a/chapter05/expect-inst.xml b/chapter05/expect-inst.xml index 84e186da9..6c861558b 100644 --- a/chapter05/expect-inst.xml +++ b/chapter05/expect-inst.xml @@ -5,14 +5,14 @@ <para>First apply a patch:</para> -<para><screen><userinput>patch -Np1 -i ../&expect-patch;</userinput></screen></para> +<screen><userinput>patch -Np1 -i ../&expect-patch;</userinput></screen> <para>This fixes a bug in Expect that can result in bogus failures during the GCC test suite run.</para> <para>Now prepare Expect to be compiled:</para> -<para><screen><userinput>./configure --prefix=/tools --with-tcl=/tools/lib --with-x=no</userinput></screen></para> +<screen><userinput>./configure --prefix=/tools --with-tcl=/tools/lib --with-x=no</userinput></screen> <para>The meaning of the configure options:</para> @@ -29,17 +29,17 @@ libraries, both of which may possibly reside on the host system.</para></listite <para>Build the package:</para> -<para><screen><userinput>make</userinput></screen></para> +<screen><userinput>make</userinput></screen> <para>This package has a test suite available which can perform a number of checks to ensure it built correctly. Should you choose to run it, the following command will do so:</para> -<para><screen><userinput>make test</userinput></screen></para> +<screen><userinput>make test</userinput></screen> <para>And install:</para> -<para><screen><userinput>make SCRIPTS="" install</userinput></screen></para> +<screen><userinput>make SCRIPTS="" install</userinput></screen> <para>The meaning of the make option:</para> diff --git a/chapter05/findutils-inst.xml b/chapter05/findutils-inst.xml index 7cad46962..45656baf5 100644 --- a/chapter05/findutils-inst.xml +++ b/chapter05/findutils-inst.xml @@ -5,20 +5,20 @@ <para>Prepare Findutils to be compiled:</para> -<para><screen><userinput>./configure --prefix=/tools</userinput></screen></para> +<screen><userinput>./configure --prefix=/tools</userinput></screen> <para>Compile the package:</para> -<para><screen><userinput>make </userinput></screen></para> +<screen><userinput>make </userinput></screen> <para>This package has a test suite available which can perform a number of checks to ensure it built correctly. Should you choose to run it, the following command will do so:</para> -<para><screen><userinput>make check</userinput></screen></para> +<screen><userinput>make check</userinput></screen> <para>And install the package:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> </sect2> diff --git a/chapter05/gawk-inst.xml b/chapter05/gawk-inst.xml index 216dfcac3..43e394804 100644 --- a/chapter05/gawk-inst.xml +++ b/chapter05/gawk-inst.xml @@ -5,21 +5,21 @@ <para>Prepare Gawk to be compiled:</para> -<para><screen><userinput>./configure --prefix=/tools</userinput></screen></para> +<screen><userinput>./configure --prefix=/tools</userinput></screen> <para>Compile the package:</para> -<para><screen><userinput>make</userinput></screen></para> +<screen><userinput>make</userinput></screen> <para>This package has a test suite available which can perform a number of checks to ensure it built correctly. Should you choose to run it, the following command will do so:</para> -<para><screen><userinput>make check</userinput></screen></para> +<screen><userinput>make check</userinput></screen> <para>And install it:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> </sect2> diff --git a/chapter05/gcc-pass1-inst.xml b/chapter05/gcc-pass1-inst.xml index d0cdf0dc3..d396405ab 100644 --- a/chapter05/gcc-pass1-inst.xml +++ b/chapter05/gcc-pass1-inst.xml @@ -20,15 +20,15 @@ or modifying them when building GCC.</para> <para>The GCC documentation recommends building GCC outside of the source directory in a dedicated build directory:</para> -<para><screen><userinput>mkdir ../gcc-build -cd ../gcc-build</userinput></screen></para> +<screen><userinput>mkdir ../gcc-build +cd ../gcc-build</userinput></screen> <para>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 \ --disable-nls --enable-shared \ - --enable-languages=c</userinput></screen></para> + --enable-languages=c</userinput></screen> <para>The meaning of the configure options:</para> @@ -55,7 +55,7 @@ have downloaded and unpacked the full GCC tarball.</para></listitem> <para>Continue with compiling the package:</para> -<para><screen><userinput>make BOOT_LDFLAGS="-static" bootstrap</userinput></screen></para> +<screen><userinput>make BOOT_LDFLAGS="-static" bootstrap</userinput></screen> <para>The meaning of the make parameters:</para> @@ -73,7 +73,7 @@ compiled correctly.</para></listitem> <para>And install the package:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> <para>As a finishing touch we'll create the <filename class="symlink">/tools/bin/cc</filename> symlink. Many programs and @@ -83,7 +83,7 @@ Unix systems. Not everybody has the GNU C compiler installed. Simply running <userinput>cc</userinput> leaves the system administrator free to decide what C compiler to install, as long as there's a symlink pointing to it:</para> -<para><screen><userinput>ln -sf gcc /tools/bin/cc</userinput></screen></para> +<screen><userinput>ln -sf gcc /tools/bin/cc</userinput></screen> </sect2> 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 diff --git a/chapter05/gettext-inst.xml b/chapter05/gettext-inst.xml index c46c65d9d..3721b6bb3 100644 --- a/chapter05/gettext-inst.xml +++ b/chapter05/gettext-inst.xml @@ -5,21 +5,21 @@ <para>Prepare Gettext to be compiled:</para> -<para><screen><userinput>./configure --prefix=/tools</userinput></screen></para> +<screen><userinput>./configure --prefix=/tools</userinput></screen> <para>Compile the programs:</para> -<para><screen><userinput>make </userinput></screen></para> +<screen><userinput>make </userinput></screen> <para>This package has a test suite available which can perform a number of checks to ensure it built correctly. Should you choose to run it, the following command will do so:</para> -<para><screen><userinput>make check</userinput></screen></para> +<screen><userinput>make check</userinput></screen> <para>Then install them and their documentation:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> </sect2> diff --git a/chapter05/glibc-inst.xml b/chapter05/glibc-inst.xml index 1a5e6659e..02c26237d 100644 --- a/chapter05/glibc-inst.xml +++ b/chapter05/glibc-inst.xml @@ -25,27 +25,27 @@ is putting the stability of your system at risk.</para> complain about the absence of <filename>/tools/etc/ld.so.conf</filename>. Fix this annoying little error with:</para> -<para><screen><userinput>mkdir /tools/etc -touch /tools/etc/ld.so.conf</userinput></screen></para> +<screen><userinput>mkdir /tools/etc +touch /tools/etc/ld.so.conf</userinput></screen> <para>Also, Glibc has a subtle problem when compiled with GCC 3.3.1. Apply the following patch to fix this:</para> -<para><screen><userinput>patch -Np1 -i ../&glibc-sscanf-patch;</userinput></screen></para> +<screen><userinput>patch -Np1 -i ../&glibc-sscanf-patch;</userinput></screen> <para>The Glibc documentation recommends building Glibc outside of the source directory in a dedicated build directory:</para> -<para><screen><userinput>mkdir ../glibc-build -cd ../glibc-build</userinput></screen></para> +<screen><userinput>mkdir ../glibc-build +cd ../glibc-build</userinput></screen> <para>Next, prepare Glibc to be compiled:</para> -<para><screen><userinput>../glibc-&glibc-version;/configure --prefix=/tools \ +<screen><userinput>../glibc-&glibc-version;/configure --prefix=/tools \ --disable-profile --enable-add-ons \ --with-headers=/tools/include \ --with-binutils=/tools/bin \ - --without-gd</userinput></screen></para> + --without-gd</userinput></screen> <para>The meaning of the configure options:</para> @@ -82,11 +82,11 @@ running the test suite.</para> <para>Compile the package:</para> -<para><screen><userinput>make</userinput></screen></para> +<screen><userinput>make</userinput></screen> <para>Run the test suite:</para> -<para><screen><userinput>make check</userinput></screen></para> +<screen><userinput>make check</userinput></screen> <para>The Glibc test suite is highly dependent on certain functions of your host system, in particular the kernel. Additionally, here in Chapter 5, some tests @@ -129,7 +129,7 @@ of failures.</para> <para>Now install the package:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> <para>Different countries and cultures have varying conventions for how to communicate. These conventions range from very simple ones, such as the format @@ -137,7 +137,7 @@ for representing dates and times, to very complex ones, such as the language spoken. This "internationalization" works by means of locales. We'll install the Glibc locales now:</para> -<para><screen><userinput>make localedata/install-locales</userinput></screen></para> +<screen><userinput>make localedata/install-locales</userinput></screen> <para>An alternative to running the previous command is to install only those locales which you need or want. This can be achieved by using the @@ -149,7 +149,7 @@ to pass correctly, in particular, the libstdc++ tests from GCC. The following instructions, instead of the install-locales command above, will install the minimum set of locales necessary for the tests to run successfully:</para> -<para><screen><userinput>mkdir -p /tools/lib/locale +<screen><userinput>mkdir -p /tools/lib/locale localedef -i de_DE -f ISO-8859-1 de_DE localedef -i de_DE@euro -f ISO-8859-15 de_DE@euro localedef -i en_HK -f ISO-8859-1 en_HK @@ -159,7 +159,7 @@ localedef -i es_MX -f ISO-8859-1 es_MX localedef -i fr_FR -f ISO-8859-1 fr_FR localedef -i fr_FR@euro -f ISO-8859-15 fr_FR@euro localedef -i it_IT -f ISO-8859-1 it_IT -localedef -i ja_JP -f EUC-JP ja_JP</userinput></screen></para> +localedef -i ja_JP -f EUC-JP ja_JP</userinput></screen> </sect2> diff --git a/chapter05/grep-inst.xml b/chapter05/grep-inst.xml index 9cbc96139..d613ed5c5 100644 --- a/chapter05/grep-inst.xml +++ b/chapter05/grep-inst.xml @@ -5,8 +5,8 @@ <para>Prepare Grep to be compiled:</para> -<para><screen><userinput>./configure --prefix=/tools \ - --disable-perl-regexp --with-included-regex</userinput></screen></para> +<screen><userinput>./configure --prefix=/tools \ + --disable-perl-regexp --with-included-regex</userinput></screen> <para>The meaning of the configure options:</para> @@ -22,17 +22,17 @@ the code from Glibc, which is known to be slightly buggy.</para></listitem> <para>Compile the programs:</para> -<para><screen><userinput>make </userinput></screen></para> +<screen><userinput>make </userinput></screen> <para>This package has a test suite available which can perform a number of checks to ensure it built correctly. Should you choose to run it, the following command will do so:</para> -<para><screen><userinput>make check</userinput></screen></para> +<screen><userinput>make check</userinput></screen> <para>Then install them and their documentation:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> </sect2> diff --git a/chapter05/gzip-inst.xml b/chapter05/gzip-inst.xml index 92f254a6a..5fc2ff79f 100644 --- a/chapter05/gzip-inst.xml +++ b/chapter05/gzip-inst.xml @@ -5,15 +5,15 @@ <para>Prepare Gzip to be compiled:</para> -<para><screen><userinput>./configure --prefix=/tools</userinput></screen></para> +<screen><userinput>./configure --prefix=/tools</userinput></screen> <para>Compile the package:</para> -<para><screen><userinput>make</userinput></screen></para> +<screen><userinput>make</userinput></screen> <para>And install it:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> </sect2> diff --git a/chapter05/introduction.xml b/chapter05/introduction.xml index 37866e207..2a31498cd 100644 --- a/chapter05/introduction.xml +++ b/chapter05/introduction.xml @@ -43,7 +43,7 @@ sake and to save space.</para> <para>Before continuing, make sure the LFS environment variable is set up properly by executing the following:</para> -<para><screen><userinput>echo $LFS</userinput></screen></para> +<screen><userinput>echo $LFS</userinput></screen> <para>Make sure the output shows the path to your LFS partition's mount point, which is <filename class="directory">/mnt/lfs</filename> if you diff --git a/chapter05/kernelheaders-inst.xml b/chapter05/kernelheaders-inst.xml index 15cf446ac..ecfa07732 100644 --- a/chapter05/kernelheaders-inst.xml +++ b/chapter05/kernelheaders-inst.xml @@ -9,7 +9,7 @@ place where <userinput>gcc</userinput> can later find them.</para> <para>Prepare for the header installation with:</para> -<para><screen><userinput>make mrproper</userinput></screen></para> +<screen><userinput>make mrproper</userinput></screen> <para>This ensures that the kernel tree is absolutely clean. The kernel team recommends that this command be issued prior to <emphasis>each</emphasis> kernel @@ -18,29 +18,29 @@ untarring.</para> <para>Create the <filename>include/linux/version.h</filename> file:</para> -<para><screen><userinput>make include/linux/version.h</userinput></screen></para> +<screen><userinput>make include/linux/version.h</userinput></screen> <para>Create the platform-specific <filename>include/asm</filename> symlink:</para> -<para><screen><userinput>make symlinks</userinput></screen></para> +<screen><userinput>make symlinks</userinput></screen> <para>Install the platform-specific header files:</para> -<para><screen><userinput>mkdir /tools/include/asm +<screen><userinput>mkdir /tools/include/asm cp include/asm/* /tools/include/asm -cp -R include/asm-generic /tools/include</userinput></screen></para> +cp -R include/asm-generic /tools/include</userinput></screen> <para>Install the cross-platform kernel header files:</para> -<para><screen><userinput>cp -R include/linux /tools/include</userinput></screen></para> +<screen><userinput>cp -R include/linux /tools/include</userinput></screen> <para>There are a few kernel header files which make use of the <filename>autoconf.h</filename> header file. Since we do not yet configure the kernel, we need to create this file ourselves in order to avoid compilation failures. Create an empty <filename>autoconf.h</filename> file:</para> -<para><screen><userinput>touch /tools/include/linux/autoconf.h</userinput></screen></para> +<screen><userinput>touch /tools/include/linux/autoconf.h</userinput></screen> </sect2> diff --git a/chapter05/lockingglibc.xml b/chapter05/lockingglibc.xml index 94ab49e91..215e7567e 100644 --- a/chapter05/lockingglibc.xml +++ b/chapter05/lockingglibc.xml @@ -10,7 +10,7 @@ specs file.</para> <para>First install the adjusted linker by running the following from within the <filename class="directory">binutils-build</filename> directory:</para> -<para><screen><userinput>make -C ld install</userinput></screen></para> +<screen><userinput>make -C ld install</userinput></screen> <para>The linker was adjusted a little while back, at the end of the first pass of Binutils. From this point onwards everything will link <emphasis>only @@ -22,11 +22,11 @@ Binutils build and source directories.</para> <para>The next thing to do is to amend our GCC specs file so that it points to the new dynamic linker. A simple sed will accomplish this:</para> -<para><screen><userinput>SPECFILE=/tools/lib/gcc-lib/*/*/specs +<screen><userinput>SPECFILE=/tools/lib/gcc-lib/*/*/specs sed -e 's@/lib/ld-linux.so.2@/tools/lib/ld-linux.so.2@g' \ $SPECFILE > tempspecfile mv tempspecfile $SPECFILE -unset SPECFILE</userinput></screen></para> +unset SPECFILE</userinput></screen> <para>We recommend that you cut-and-paste the above rather than try and type it all in. Or you can edit the specs file by hand if you want to: just replace any @@ -44,15 +44,15 @@ because of GCC's "fixincludes" process which runs as part of the GCC build. We'll explain more about this further on in this chapter. For now, run the following commands to eliminate this possibility:</para> -<para><screen><userinput>rm -f /tools/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen></para> +<screen><userinput>rm -f /tools/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen> <caution><para>It is imperative at this point to stop and ensure that the basic functions (compiling and linking) of the new toolchain are working as expected. For this we are going to perform a simple sanity check:</para> -<para><screen><userinput>echo 'main(){}' > dummy.c +<screen><userinput>echo 'main(){}' > dummy.c gcc dummy.c -readelf -l a.out | grep ': /tools'</userinput></screen></para> +readelf -l a.out | grep ': /tools'</userinput></screen> <para>If everything is working correctly, there should be no errors, and the output of the last command will be:</para> @@ -71,7 +71,7 @@ different.</para> <para>Once you are satisfied that all is well, clean up the test files:</para> -<para><screen><userinput>rm dummy.c a.out</userinput></screen></para> +<screen><userinput>rm dummy.c a.out</userinput></screen> </caution> <para>This completes the installation of the self-contained toolchain, and it diff --git a/chapter05/make-inst.xml b/chapter05/make-inst.xml index 9c41b3e5e..d9e32bff7 100644 --- a/chapter05/make-inst.xml +++ b/chapter05/make-inst.xml @@ -5,21 +5,21 @@ <para>Prepare Make to be compiled:</para> -<para><screen><userinput>./configure --prefix=/tools</userinput></screen></para> +<screen><userinput>./configure --prefix=/tools</userinput></screen> <para>Compile the program:</para> -<para><screen><userinput>make </userinput></screen></para> +<screen><userinput>make </userinput></screen> <para>This package has a test suite available which can perform a number of checks to ensure it built correctly. Should you choose to run it, the following command will do so:</para> -<para><screen><userinput>make check</userinput></screen></para> +<screen><userinput>make check</userinput></screen> <para>Then install it and its documentation:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> </sect2> diff --git a/chapter05/ncurses-inst.xml b/chapter05/ncurses-inst.xml index 7c187a2b5..dea216194 100644 --- a/chapter05/ncurses-inst.xml +++ b/chapter05/ncurses-inst.xml @@ -5,8 +5,8 @@ <para>Fix two minor things:</para> -<para><screen><userinput>patch -Np1 -i ../&ncurses-etip-patch; -patch -Np1 -i ../&ncurses-vsscanf-patch;</userinput></screen></para> +<screen><userinput>patch -Np1 -i ../&ncurses-etip-patch; +patch -Np1 -i ../&ncurses-vsscanf-patch;</userinput></screen> <para>The first patch corrects the <filename>etip.h</filename> header file, and the second patch prevents some compiler warnings being issued on the use of @@ -14,8 +14,8 @@ deprecated headers.</para> <para>Now prepare Ncurses to be compiled:</para> -<para><screen><userinput>./configure --prefix=/tools --with-shared \ - --without-debug --without-ada --enable-overwrite</userinput></screen></para> +<screen><userinput>./configure --prefix=/tools --with-shared \ + --without-debug --without-ada --enable-overwrite</userinput></screen> <para>The meaning of the configure options:</para> @@ -33,11 +33,11 @@ ensure that other packages can find the Ncurses headers successfully.</para> <para>Compile the programs and libraries:</para> -<para><screen><userinput>make </userinput></screen></para> +<screen><userinput>make </userinput></screen> <para>Then install them and their documentation:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> </sect2> diff --git a/chapter05/patch-inst.xml b/chapter05/patch-inst.xml index 3b5badbb3..a04fec408 100644 --- a/chapter05/patch-inst.xml +++ b/chapter05/patch-inst.xml @@ -5,18 +5,18 @@ <para>Prepare Patch to be compiled:</para> -<para><screen><userinput>CPPFLAGS=-D_GNU_SOURCE ./configure --prefix=/tools</userinput></screen></para> +<screen><userinput>CPPFLAGS=-D_GNU_SOURCE ./configure --prefix=/tools</userinput></screen> <para>The preprocessor flag <userinput>-D_GNU_SOURCE</userinput> is only needed on the PowerPC platform. On other architectures you can leave it out.</para> <para>Compile the program:</para> -<para><screen><userinput>make </userinput></screen></para> +<screen><userinput>make </userinput></screen> <para>Then install it and its documentation:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> </sect2> diff --git a/chapter05/perl-inst.xml b/chapter05/perl-inst.xml index 297fe7aef..65467b194 100644 --- a/chapter05/perl-inst.xml +++ b/chapter05/perl-inst.xml @@ -4,26 +4,26 @@ <para>First adapt some hard-wired paths to the C library:</para> -<para><screen><userinput>patch -Np1 -i ../&perl-libc-patch;</userinput></screen></para> +<screen><userinput>patch -Np1 -i ../&perl-libc-patch;</userinput></screen> <para>And make sure some static extensions get built:</para> -<para><screen><userinput>chmod u+w hints/linux.sh -echo 'static_ext="IO re Fcntl"' >> hints/linux.sh</userinput></screen></para> +<screen><userinput>chmod u+w hints/linux.sh +echo 'static_ext="IO re Fcntl"' >> hints/linux.sh</userinput></screen> <para>Now prepare Perl for compilation:</para> -<para><screen><userinput>./configure.gnu --prefix=/tools</userinput></screen></para> +<screen><userinput>./configure.gnu --prefix=/tools</userinput></screen> <para>Compile only the required tools:</para> -<para><screen><userinput>make perl utilities</userinput></screen></para> +<screen><userinput>make perl utilities</userinput></screen> <para>Then copy these tools and their libraries:</para> -<para><screen><userinput>cp perl pod/pod2man /tools/bin +<screen><userinput>cp perl pod/pod2man /tools/bin mkdir -p /tools/lib/perl5/5.8.0 -cp -R lib/* /tools/lib/perl5/5.8.0</userinput></screen></para> +cp -R lib/* /tools/lib/perl5/5.8.0</userinput></screen> </sect2> diff --git a/chapter05/sed-inst.xml b/chapter05/sed-inst.xml index eaee0cd07..7ea6c6bf3 100644 --- a/chapter05/sed-inst.xml +++ b/chapter05/sed-inst.xml @@ -5,21 +5,21 @@ <para>Prepare Sed to be compiled:</para> -<para><screen><userinput>./configure --prefix=/tools</userinput></screen></para> +<screen><userinput>./configure --prefix=/tools</userinput></screen> <para>Compile the program:</para> -<para><screen><userinput>make </userinput></screen></para> +<screen><userinput>make </userinput></screen> <para>This package has a test suite available which can perform a number of checks to ensure it built correctly. Should you choose to run it, the following command will do so:</para> -<para><screen><userinput>make check</userinput></screen></para> +<screen><userinput>make check</userinput></screen> <para>Then install it and its documentation:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> </sect2> diff --git a/chapter05/setting-environment.xml b/chapter05/setting-environment.xml index 05d4a9a23..413908917 100644 --- a/chapter05/setting-environment.xml +++ b/chapter05/setting-environment.xml @@ -5,7 +5,7 @@ <para>While logged in as user <emphasis>lfs</emphasis>, issue the following commands to set up a good work environment:</para> -<para><screen><userinput>cat > ~/.bash_profile << "EOF"</userinput> +<screen><userinput>cat > ~/.bash_profile << "EOF"</userinput> set +h umask 022 LFS=/mnt/lfs @@ -15,7 +15,7 @@ export LFS LC_ALL PATH unset CC CXX CPP LD_LIBRARY_PATH LD_PRELOAD <userinput>EOF -source ~/.bash_profile</userinput></screen></para> +source ~/.bash_profile</userinput></screen> <para>The <userinput>set +h</userinput> command turns off <userinput>bash</userinput>'s hash function. Normally hashing is a useful diff --git a/chapter05/tar-inst.xml b/chapter05/tar-inst.xml index f9e2bed56..47c47ae88 100644 --- a/chapter05/tar-inst.xml +++ b/chapter05/tar-inst.xml @@ -5,21 +5,21 @@ <para>Prepare Tar to be compiled:</para> -<para><screen><userinput>./configure --prefix=/tools</userinput></screen></para> +<screen><userinput>./configure --prefix=/tools</userinput></screen> <para>Compile the programs:</para> -<para><screen><userinput>make </userinput></screen></para> +<screen><userinput>make </userinput></screen> <para>This package has a test suite available which can perform a number of checks to ensure it built correctly. Should you choose to run it, the following command will do so:</para> -<para><screen><userinput>make check</userinput></screen></para> +<screen><userinput>make check</userinput></screen> <para>Then install them and their documentation:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> </sect2> diff --git a/chapter05/tcl-inst.xml b/chapter05/tcl-inst.xml index bba3f152b..5d93829ee 100644 --- a/chapter05/tcl-inst.xml +++ b/chapter05/tcl-inst.xml @@ -10,18 +10,18 @@ to know that our most important tools are working properly.</para> <para>Prepare Tcl to be compiled:</para> -<para><screen><userinput>cd unix -./configure --prefix=/tools</userinput></screen></para> +<screen><userinput>cd unix +./configure --prefix=/tools</userinput></screen> <para>Build the package:</para> -<para><screen><userinput>make</userinput></screen></para> +<screen><userinput>make</userinput></screen> <para>This package has a test suite available which can perform a number of checks to ensure it built correctly. Should you choose to run it, the following command will do so:</para> -<para><screen><userinput>TZ=UTC make test</userinput></screen></para> +<screen><userinput>TZ=UTC make test</userinput></screen> <para>The meaning of the make option:</para> @@ -40,10 +40,10 @@ throughout the book.</para> <para>Install the package:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> <para>Make a necessary symbolic link:</para> -<para><screen><userinput>ln -s tclsh8.4 /tools/bin/tclsh</userinput></screen></para> +<screen><userinput>ln -s tclsh8.4 /tools/bin/tclsh</userinput></screen> <caution><para>Do not remove the <filename>tcl&tcl-version;</filename> source directory yet, as the next package diff --git a/chapter05/texinfo-inst.xml b/chapter05/texinfo-inst.xml index c991473e3..415226e4a 100644 --- a/chapter05/texinfo-inst.xml +++ b/chapter05/texinfo-inst.xml @@ -5,21 +5,21 @@ <para>Prepare Texinfo to be compiled:</para> -<para><screen><userinput>./configure --prefix=/tools</userinput></screen></para> +<screen><userinput>./configure --prefix=/tools</userinput></screen> <para>Compile the programs:</para> -<para><screen><userinput>make </userinput></screen></para> +<screen><userinput>make </userinput></screen> <para>This package has a test suite available which can perform a number of checks to ensure it built correctly. Should you choose to run it, the following command will do so:</para> -<para><screen><userinput>make check</userinput></screen></para> +<screen><userinput>make check</userinput></screen> <para>Then install them and their documentation:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> </sect2> diff --git a/chapter05/utillinux-inst.xml b/chapter05/utillinux-inst.xml index 26598be97..7d0cda535 100644 --- a/chapter05/utillinux-inst.xml +++ b/chapter05/utillinux-inst.xml @@ -6,26 +6,26 @@ <para>Util-linux doesn't use the freshly installed headers and libraries from the /tools directory. This is fixed by altering the configure script:</para> -<para><screen><userinput>cp configure configure.backup -sed "s@/usr/include@/tools/include@g" configure.backup > configure</userinput> </screen></para> +<screen><userinput>cp configure configure.backup +sed "s@/usr/include@/tools/include@g" configure.backup > configure</userinput> </screen> <para>Prepare Util-linux for compilation:</para> -<para><screen><userinput>./configure</userinput></screen></para> +<screen><userinput>./configure</userinput></screen> <para>Compile some support routines:</para> -<para><screen><userinput>make -C lib</userinput></screen></para> +<screen><userinput>make -C lib</userinput></screen> <para>And, since you'll need only a couple of the utilities contained in this package, build just those:</para> -<para><screen><userinput>make -C mount mount umount -make -C text-utils more</userinput></screen></para> +<screen><userinput>make -C mount mount umount +make -C text-utils more</userinput></screen> <para>Now copy these programs to the temporary tools directory:</para> -<para><screen><userinput>cp mount/{,u}mount text-utils/more /tools/bin</userinput></screen></para> +<screen><userinput>cp mount/{,u}mount text-utils/more /tools/bin</userinput></screen> </sect2> |