- Timestamp:
- 01/30/2006 06:51:33 AM (18 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 16328ae
- Parents:
- 62d3362
- Location:
- chapter06
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/binutils.xml
r62d3362 r28bb0634 60 60 <screen><userinput>make tooldir=/usr</userinput></screen> 61 61 62 <para>Normally, the tooldir (the directory where the executables will ultimately 63 be located) is set to <filename 64 class="directory">$(exec_prefix)/$(target_alias)</filename>. For example, i686 65 machines would expand that to <filename 66 class="directory">/usr/i686-pc-linux-gnu</filename>. Because this is a custom 67 system, this target-specific directory in <filename 68 class="directory">/usr</filename> is not required. <filename 69 class="directory">$(exec_prefix)/$(target_alias)</filename> would be used if the 70 system was used to cross-compile (for example, compiling a package on an Intel 71 machine that generates code that can be executed on PowerPC machines).</para> 62 <variablelist> 63 <title>The meaning of the make parameter:</title> 64 <varlistentry> 65 <term><parameter>tooldir=/usr</parameter></term> 66 <listitem> 67 <para>Normally, the tooldir (the directory where the executables will 68 ultimately be located) is set to <filename 69 class="directory">$(exec_prefix)/$(target_alias)</filename>. For 70 example, i686 machines would expand that to <filename 71 class="directory">/usr/i686-pc-linux-gnu</filename>. Because this is 72 a custom system, this target-specific directory in <filename 73 class="directory">/usr</filename> is not required. <filename 74 class="directory">$(exec_prefix)/$(target_alias)</filename> would be 75 used if the system was used to cross-compile (for example, compiling a 76 package on an Intel machine that generates code that can be executed 77 on PowerPC machines).</para> 78 </listitem> 79 </varlistentry> 80 </variablelist> 72 81 73 82 <important><para>The test suite for Binutils in this section is -
chapter06/changingowner.xml
r62d3362 r28bb0634 33 33 <para>The command uses <parameter>0:0</parameter> instead of 34 34 <parameter>root:root</parameter>, because <command>chown</command> 35 is unable to resolve the name <quote>root</quote> until the password 36 file has been created. This book assumes you ran this 37 <command>chown</command> command.</para> 35 is unable to resolve the name <quote>root</quote> until the 36 <filename>passwd</filename> file has been created.</para> 38 37 39 38 </sect1> -
chapter06/strippingagain.xml
r62d3362 r28bb0634 18 18 render the new system unusable, so before running the 19 19 <command>strip</command> command, it is a good idea to make a 20 backup of the current situation.</para>20 backup of the LFS system in its current state.</para> 21 21 22 22 <para>Before performing the stripping, take special care to ensure that -
chapter06/vim.xml
r62d3362 r28bb0634 114 114 115 115 <sect2 id="conf-vim" role="configuration"><title>Configuring Vim</title> 116 <indexterm zone="conf-vim"><primary sortas="e-/etc/vim ">/etc/vim</primary></indexterm>116 <indexterm zone="conf-vim"><primary sortas="e-/etc/vimrc">/etc/vimrc</primary></indexterm> 117 117 118 118 <para>By default, <command>vim</command> runs in vi-incompatible mode. This may
Note:
See TracChangeset
for help on using the changeset viewer.