Context Navigation

rc288d97	r90e3cb3
38	38
39	39	<para>To remove debugging symbols from a binary (which must be an a.out
40		or ELF binary), run <~~userinput>strip --strip-debug filename</userinput~~>.
	40	or ELF binary), run <command>strip --strip-debug filename</command>.
41	41	Wildcards can be used to treat multiple files (use something like
42	42	<userinput>strip --strip-debug $LFS/tools/bin/*</userinput>).</para>

chapter06/bash.xml

rc288d97	r90e3cb3
40	40	<screen><userinput>make install</userinput></screen>
41	41
42		<para>And reload the newly compiled <~~userinput>bash</userinput~~> program:</para>
	42	<para>And reload the newly compiled <command>bash</command> program:</para>
43	43
44	44	<screen><userinput>exec /bin/bash --login +h</userinput></screen>

chapter06/bzip2.xml

-              rc288d97
+              r90e3cb3
 <para>The Bzip2 package contains programs for compressing and decompressing
 files. On text files they achieve a much better compression than the
 traditional <userinput>gzip</userinput>.</para>
+traditional <command>gzip</command>.</para>
 <screen>&buildtime; &bzip2-time;
 …
 <para>If you are reinstalling Bzip2, you will now first have to do
 <userinput>rm -f /usr/bin/bz*</userinput>, otherwise the following
 <userinput>make install</userinput> will fail.</para>
+<command>make install</command> will fail.</para>
 <para>Install the programs:</para>
 …
 <screen><userinput>make install</userinput></screen>
 <para>And install the shared <userinput>bzip2</userinput> binary into the
+<para>And install the shared <command>bzip2</command> binary into the
 <filename class="directory">/bin</filename> directory, then make some
 necessary symbolic links, and clean up:</para>

chapter06/chapter06.xml

-              rc288d97
+              r90e3cb3
 the packages we need. Before you can chroot, however, you need to become
 <emphasis>root</emphasis>, since only <emphasis>root</emphasis>
 can execute the <userinput>chroot</userinput> command.</para>
+can execute the <command>chroot</command> command.</para>
 <para>Just like earlier, ensure the LFS environment variable is set up properly
 by running <userinput>echo $LFS</userinput> and ensuring it shows the path to
 your LFS partition's mount point, which is
+<filename class="directory">/mnt/lfs</filename> if you followed our
+example.</para>
+<filename class="directory">/mnt/lfs</filename> if you followed our example.</para>
 <para>Become <emphasis>root</emphasis> and run the following command
 …
 &nbsp;&nbsp;&nbsp;&nbsp;/tools/bin/bash --login +h</userinput></screen>
 <para>The <userinput>-i</userinput> option given to the
 <userinput>env</userinput> command will clear all variables of the chroot
+<para>The <emphasis>-i</emphasis> option given to the
+<command>env</command> command will clear all variables of the chroot
 environment. After that, only the HOME, TERM, PS1 and PATH variables are
 set again. The TERM=$TERM construct will set the TERM variable inside chroot
 to the same value as outside chroot; this variable is needed for programs
 like <userinput>vim</userinput> and <userinput>less</userinput> to operate
+like <command>vim</command> and <command>less</command> to operate
 properly. If you need other variables present, such as CFLAGS or CXXFLAGS,
 this is a good place to set them again.</para>
 …
 as soon as its final version is installed. Well, at least when the shell
 doesn't remember the locations of executed binaries -- for this reason hashing
 is switched off by passing the <userinput>+h</userinput> option to
 <userinput>bash</userinput>.</para>
+is switched off by passing the <emphasis>+h</emphasis> option to
+<command>bash</command>.</para>
 <para>You have to make sure all the commands in the rest of this chapter and
 …
 <screen><userinput>exec /tools/bin/bash --login +h</userinput></screen>
 <para>Note the use of the <userinput>+h</userinput> directive. This tells
 <userinput>bash</userinput> not to use its internal path hashing. Without this
 directive, <userinput>bash</userinput> would remember the paths to binaries it
+<para>Note the use of the <emphasis>+h</emphasis> directive. This tells
+<command>bash</command> not to use its internal path hashing. Without this
+directive, <command>bash</command> would remember the paths to binaries it
 has executed. Since we want to use our newly compiled binaries as soon as
 they are installed, we turn off this function for the duration of this
 chapter.</para>
 <para>The <userinput>login</userinput>, <userinput>agetty</userinput> and
 <userinput>init</userinput> programs (and some others) use a number of log
+<para>The <command>login</command>, <command>agetty</command> and
+<command>init</command> programs (and some others) use a number of log
 files to record information such as who was logged into the system and when.
 These programs, however, won't write to the log files if they don't already
 …
 against the libraries in <filename>/usr/lib</filename> and
 <filename>/lib</filename>. The extra
 <userinput>INSTALL=/tools/bin/install</userinput> is needed because the Makefile
+<emphasis>INSTALL=/tools/bin/install</emphasis> is needed because the Makefile
 created during the second pass still contains the reference to
 <filename>/usr/bin/install</filename>, which we obviously haven't installed yet.

chapter06/config-glibc.xml

rc288d97	r90e3cb3
55	55
56	56	<para>Of course, instead of <emphasis>Canada/Eastern</emphasis>, fill in
57		the name of the time zone that the <~~userinput>tzselect</userinput~~> script
	57	the name of the time zone that the <command>tzselect</command> script
58	58	gave you.</para>
59	59

chapter06/config-shadowpwd.xml

-              rc288d97
+              r90e3cb3
 <para>Under normal circumstances, you won't have created any passwords yet.
 However, if returning to this section to enable shadowing, you should reset any
 current user passwords with the <userinput>passwd</userinput> command or any
 group passwords with the <userinput>gpasswd</userinput> command.</para>
+current user passwords with the <command>passwd</command> command or any
+group passwords with the <command>gpasswd</command> command.</para>
 </sect2>

chapter06/config-vim.xml

-              rc288d97
+              r90e3cb3
 <sect2><title>Configuring Vim</title>
 <para>By default, <userinput>vim</userinput> runs in vi-compatible mode. Some
 people might like this, but we prefer to run <userinput>vim</userinput> in its
+<para>By default, <command>vim</command> runs in vi-compatible mode. Some
+people might like this, but we prefer to run <command>vim</command> in its
 own mode (else we wouldn't have included it in this book, but the original
 <userinput>vi</userinput>). Create a default vim configuration file by running
+<command>vi</command>). Create a default vim configuration file by running
 the following:</para>
 …
 <userinput>EOF</userinput></screen>
 <para>The <userinput>set nocompatible</userinput> will make
 <userinput>vim</userinput> behave in a more useful way than the default
 vi-compatible manner. The <userinput>set backspace=2</userinput> allows
+<para>The <emphasis>set nocompatible</emphasis> will make
+<command>vim</command> behave in a more useful way than the default
+vi-compatible manner. The <emphasis>set backspace=2</emphasis> allows
 backspacing over line breaks, autoindent and the start of insert. And the
 <userinput>syntax on</userinput> switches on <userinput>vim</userinput>'s
+<emphasis>syntax on</emphasis> switches on <command>vim</command>'s
 semantic colouring.</para>

chapter06/coreutils.xml

-              rc288d97
+              r90e3cb3
 <screen><userinput>patch -Np1 -i ../&coreutils-posixver-patch;</userinput></screen>
 <para>Normally the functionality of <userinput>uname</userinput> is somewhat
 broken, in that the <userinput>-p</userinput> switch always returns "unknown".
+<para>Normally the functionality of <command>uname</command> is somewhat
+broken, in that the <emphasis>-p</emphasis> switch always returns "unknown".
 The following patch fixes this behaviour for Intel architectures:</para>
 …
 <para>We do not want Coreutils to install its version of the
 <userinput>hostname</userinput> program, because it is inferior to the version
+<command>hostname</command> program, because it is inferior to the version
 provided by Net-tools. Prevent its installation by applying a patch:</para>
 …
 <screen><userinput>make</userinput></screen>
 <para>The <userinput>su</userinput> program from Coreutils wasn't installed in
+<para>The <command>su</command> program from Coreutils wasn't installed in
 Chapter 5 because it needed <emphasis>root</emphasis> privilege to do so. We're
 going to need it in a few moments for the test suite. Therefore we work around

chapter06/flex.xml

-              rc288d97
+              r90e3cb3
 <screen><userinput>ln -s libfl.a /usr/lib/libl.a</userinput></screen>
 <para>A few programs don't know about <userinput>flex</userinput> yet and try
 to run its predecessor <userinput>lex</userinput>. To support those programs,
+<para>A few programs don't know about <command>flex</command> yet and try
+to run its predecessor <command>lex</command>. To support those programs,
 create a shell script named <filename>lex</filename> that calls
 <userinput>flex</userinput> in Lex emulation mode:</para>
+<command>flex</command> in Lex emulation mode:</para>
 <screen><userinput>cat &gt; /usr/bin/lex &lt;&lt; "EOF"</userinput>

chapter06/gcc.xml

rc288d97	r90e3cb3
87	87	<screen><userinput>ln -s ../usr/bin/cpp /lib</userinput></screen>
88	88
89		<para>Many packages use the name <~~userinput>cc</userinput~~> to call the C
	89	<para>Many packages use the name <command>cc</command> to call the C
90	90	compiler. To satisfy those packages, create a symlink:</para>
91	91

chapter06/glibc.xml

rc288d97	r90e3cb3
92	92	<para>An alternative to running the previous command is to install only those
93	93	locales which you need or want. This can be achieved by using the
94		<~~userinput>localedef</userinput~~> command. Information on this can be found in
	94	<command>localedef</command> command. Information on this can be found in
95	95	the <filename>INSTALL</filename> file in the Glibc source. However, there are
96	96	a number of locales that are essential for the tests of future packages to

chapter06/groff.xml

rc288d97	r90e3cb3
33	33	<screen><userinput>make install</userinput></screen>
34	34
35		<para>Some documentation programs, such as <~~userinput>xman</userinput~~>,
	35	<para>Some documentation programs, such as <command>xman</command>,
36	36	will not work properly without the following symlinks:</para>
37	37

chapter06/gzip.xml

-              rc288d97
+              r90e3cb3
 <screen><userinput>./configure --prefix=/usr</userinput></screen>
 <para>The <userinput>gzexe</userinput> script has the location of the
 <userinput>gzip</userinput> binary hard-wired into it. Because we later change
+<para>The <command>gzexe</command> script has the location of the
+<command>gzip</command> binary hard-wired into it. Because we later change
 the location of the binary, the following command assures that the new
 location gets placed into the script:</para>

chapter06/inetutils.xml

rc288d97	r90e3cb3
62	62	<screen><userinput>make install</userinput></screen>
63	63
64		<para>And move the <~~userinput>ping</userinput~~> program to its proper place:</para>
	64	<para>And move the <command>ping</command> program to its proper place:</para>
65	65
66	66	<screen><userinput>mv /usr/bin/ping /bin</userinput></screen>

chapter06/kbd.xml

-              rc288d97
+              r90e3cb3
 <title>Installation of Kbd</title>
 <para>By default some of Kbd's utilities (<userinput>setlogcons</userinput>,
 <userinput>setvesablank</userinput> and <userinput>getunimap</userinput>) are
+<para>By default some of Kbd's utilities (<command>setlogcons</command>,
+<command>setvesablank</command> and <command>getunimap</command>) are
 not installed. First enable the compilation of these utilities:</para>

chapter06/lfs-utils.xml

rc288d97	r90e3cb3
24	24	<itemizedlist>
25	25	<listitem><para><userinput>--with-libc</userinput>: This causes the
26		<~~userinput>mktemp</userinput~~> program to use the <emphasis>mkstemp</emphasis>
	26	<command>mktemp</command> program to use the <emphasis>mkstemp</emphasis>
27	27	and <emphasis>mkdtemp</emphasis> functions from the system C
28	28	library.</para></listitem>

chapter06/makedev.xml

-              rc288d97
+              r90e3cb3
 <para>Note that unpacking the <filename>MAKEDEV-&makedev-version;.bz2</filename>
 file doesn't create a directory for you to <userinput>cd</userinput> into, as
+file doesn't create a directory for you to <command>cd</command> into, as
 the file contains only a shell script.</para>
 <para>Install the <userinput>MAKEDEV</userinput> script:</para>
+<para>Install the <command>MAKEDEV</command> script:</para>
 <screen><userinput>bzcat MAKEDEV-&makedev-version;.bz2 &gt; /dev/MAKEDEV
 …
 <listitem><para><userinput>generic-nopty</userinput>: This instructs
 <userinput>MAKEDEV</userinput> to create a generic selection of commonly used
+<command>MAKEDEV</command> to create a generic selection of commonly used
 device special files, except for the ptyXX and ttyXX range of files. We don't
 need those files because we are going to use Unix98 PTYs via the
 …
 <para>If it turns out that some special device <filename>zzz</filename> that
 you need is missing, try running <userinput>./MAKEDEV -v zzz</userinput>.
 Alternatively, you may create devices via the <userinput>mknod</userinput>
+Alternatively, you may create devices via the <command>mknod</command>
 program. Please refer to its man and info pages if you need more
 information.</para>

chapter06/man.xml

-              rc288d97
+              r90e3cb3
 <para>The third is also a sed substitution to comment out the "MANPATH
 /usr/man" line in the <filename>man.conf</filename> file to prevent redundant
 results when using programs such as <userinput>whatis</userinput>:</para>
+results when using programs such as <command>whatis</command>:</para>
 <screen><userinput>sed -i 's%MANPATH./usr/man%#&amp;%' src/man.conf.in</userinput></screen>
 …
 <listitem><para><userinput>-confdir=/etc</userinput>: This tells the
 <userinput>man</userinput> program to look for the <filename>man.conf</filename>
+<command>man</command> program to look for the <filename>man.conf</filename>
 configuration file in the <filename>/etc</filename> directory.</para></listitem>
 </itemizedlist>
 …
 <screen><userinput>make install</userinput></screen>
 <note><para>If you wish to disable SGR escape sequences, you should
+edit the man.conf file and add the <userinput>-c</userinput> argument
 to nroff.</para></note>
+<note><para>If you wish to disable SGR escape sequences, you should edit the
+<filename>man.conf</filename> file and add the <emphasis>-c</emphasis> switch
+to NROFF.</para></note>
 <para>You may want to also take a look at the BLFS page at

chapter06/mountproc.xml

rc288d97	r90e3cb3
45	45	without support for the devpts file system. You can check which file systems
46	46	your kernel supports by peeking into its internals with a command such as
47		<~~userinput>cat /proc/filesystems</userinput~~>. If a file system type named
	47	<command>cat /proc/filesystems</command>. If a file system type named
48	48	<emphasis>devfs</emphasis> is listed there, then we'll be able to work around
49	49	the problem by mounting the host's devfs file system on top of the new

chapter06/nettools.xml

-              rc288d97
+              r90e3cb3
 <para>If you don't know what to answer to all the questions asked during the
 <userinput>make config</userinput> phase below, then just accept the defaults.
+<command>make config</command> phase below, then just accept the defaults.
 This will be just fine in the majority of cases. What you're asked here is a
 bunch of questions about which network protocols you've enabled in your
 …
 <para>If you intend to accept the default settings, you may skip the
 questions generated by <emphasis>make config</emphasis> by running
+questions generated by <command>make config</command> by running
 <userinput>yes "" | make config</userinput> instead.</para>

chapter06/patch.xml

rc288d97	r90e3cb3
20	20	<screen><userinput>CPPFLAGS=-D_GNU_SOURCE ./configure --prefix=/usr</userinput></screen>
21	21
22		<para>Again, the preprocessor flag <~~userinput>-D_GNU_SOURCE</userinput~~> is only
	22	<para>Again, the preprocessor flag <emphasis>-D_GNU_SOURCE</emphasis> is only
23	23	needed on the PowerPC platform. On other architectures you can leave it out.</para>
24	24

chapter06/perl.xml

rc288d97	r90e3cb3
23	23
24	24	<para>If you want more control over the way Perl sets itself up to be
25		built, you can run the interactive <~~userinput>Configure</userinput~~> script
	25	built, you can run the interactive <command>Configure</command> script
26	26	instead and modify the way Perl is built. If you think you can live with the
27	27	(sensible) defaults Perl auto-detects, then just use the command listed

chapter06/psmisc.xml

-              rc288d97
+              r90e3cb3
 ln -sf pstree /usr/bin/pstree.x11</userinput></screen>
 <para>By default Psmisc's <userinput>pidof</userinput> program isn't installed.
+<para>By default Psmisc's <command>pidof</command> program isn't installed.
 Generally, this isn't a problem because we later install the Sysvinit package,
 which provides a better <userinput>pidof</userinput> program. But if you're not
+which provides a better <command>pidof</command> program. But if you're not
 going to use Sysvinit, you should complete the installation of Psmisc by
 creating the following symlink:</para>

chapter06/shadowpwd.xml

-              rc288d97
+              r90e3cb3
 <title>Installation of Shadow</title>
 <para>Shadow hard-wires the path to the <userinput>passwd</userinput> binary
+<para>Shadow hard-wires the path to the <command>passwd</command> binary
 within the binary itself, but does this the wrong way. If a
 <userinput>passwd</userinput> binary is not present before installing Shadow,
+<command>passwd</command> binary is not present before installing Shadow,
 the package incorrectly assumes it is going to be located at
 <filename>/bin/passwd</filename>, but then installs it in
 …
 <screen><userinput>mkdir /etc/default</userinput></screen>
 <para>Coreutils has already installed a better <userinput>groups</userinput>
+<para>Coreutils has already installed a better <command>groups</command>
 program in <filename>/usr/bin</filename>. Remove the one installed by
 Shadow:</para>

chapter06/utillinux.xml

-              rc288d97
+              r90e3cb3
 <para>The FHS recommends that we use <filename>/var/lib/hwclock</filename>,
 instead of the usual <filename>/etc</filename>, as the location for the
 <filename>adjtime</filename> file. To make the <userinput>hwclock</userinput>
+<filename>adjtime</filename> file. To make the <command>hwclock</command>
 program FHS-compliant, run the following:</para>
 …
 <itemizedlist>
 <listitem><para><userinput>HAVE_KILL=yes</userinput>: This prevents the
 <userinput>kill</userinput> program (already installed by Procps) from being
+<command>kill</command> program (already installed by Procps) from being
 built and installed again.</para></listitem>
 <listitem><para><userinput>HAVE_SLN=yes</userinput>: This prevents the
 <userinput>sln</userinput> program (a statically linked
 <userinput>ln</userinput>, already installed by Glibc) from being built and
+<command>sln</command> program (a statically linked
+<command>ln</command>, already installed by Glibc) from being built and
 installed again.</para></listitem>
 </itemizedlist>

chapter06/vim.xml

rc288d97	r90e3cb3
53	53	<screen><userinput>make install</userinput></screen>
54	54
55		<para>When called as <~~userinput>vi</userinput>, <userinput>vim</userinput~~>
	55	<para>When called as <command>vi</command>, <command>vim</command>
56	56	will run in old-fashioned vi-mode. To allow this, create a symlink:</para>
57	57

Note: See TracChangeset for help on using the changeset viewer.

Context Navigation

Changeset 90e3cb3 for chapter06

Legend:

Download in other formats: