- Timestamp:
- 12/19/2004 07:50:52 PM (19 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.1, 6.1.1, 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:
- e431af69
- Parents:
- 86ca6e7
- Location:
- chapter04
- Files:
-
- 6 edited
-
aboutlfs.xml (modified) (2 diffs)
-
aboutsbus.xml (modified) (3 diffs)
-
abouttestsuites.xml (modified) (3 diffs)
-
addinguser.xml (modified) (3 diffs)
-
creatingtoolsdir.xml (modified) (3 diffs)
-
settingenviron.xml (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
-
chapter04/aboutlfs.xml
r86ca6e7 rae79672 8 8 <?dbhtml filename="aboutlfs.html"?> 9 9 10 <para>See testing</para> 11 12 <!-- 10 13 <para>Throughout this book the environment variable LFS will be used several 11 14 times. It is paramount that this variable is always defined. It should be set … … 30 33 reenter the environment (as when doing a <quote>su</quote> to root or another user). 31 34 </para> 35 --> 32 36 33 37 </sect1> -
chapter04/aboutsbus.xml
r86ca6e7 rae79672 8 8 <?dbhtml filename="aboutsbus.html"?> 9 9 10 <para>See testing</para> 11 12 <!-- 10 13 <para>Most people would like to know beforehand approximately how long it 11 14 takes to compile and install each package. But <quote>Linux from Scratch</quote> is built … … 13 16 anywhere near accurate: the biggest package (Glibc) won't take more than 14 17 twenty minutes on the fastest systems, but will take something like three days 15 on the slowest - -no kidding. So instead of giving actual times, we've come up18 on the slowest - no kidding. So instead of giving actual times, we've come up 16 19 with the idea of using the <emphasis>Static Binutils Unit</emphasis> 17 20 (abbreviated to <emphasis>SBU</emphasis>).</para> … … 41 44 <para>If you wish to see actual timings for specific machines, have a look at 42 45 <ulink url="&lfs-root;~bdubbs/"/>.</para> 46 --> 43 47 44 48 </sect1> -
chapter04/abouttestsuites.xml
r86ca6e7 rae79672 8 8 <?dbhtml filename="abouttestsuites.html"?> 9 9 10 <para>See testing</para> 11 12 <!-- 10 13 <para>Most packages provide a test suite. Running the test suite for a newly 11 14 built package is generally a good idea, as it can provide a nice sanity check … … 15 18 16 19 <para>Some test suites are more important than others. For example, the test 17 suites for the core toolchain packages - - GCC, Binutils, and Glibc -- are of20 suites for the core toolchain packages - GCC, Binutils, and Glibc - are of 18 21 the utmost importance due to their central role in a properly functioning 19 22 system. But be warned, the test suites for GCC and Glibc can take a very long … … 41 44 consult the LFS Wiki at <ulink url="&wiki-root;"/> to verify that these 42 45 failures are normal. This applies to all tests throughout the book.</para> 46 --> 43 47 44 48 </sect1> -
chapter04/addinguser.xml
r86ca6e7 rae79672 8 8 <?dbhtml filename="addinguser.html"?> 9 9 10 <!-- 10 11 <para>When logged in as <emphasis>root</emphasis>, making a single mistake 11 12 can damage or even wreck your system. Therefore we recommend that you … … 16 17 use this one during the installation process. As <emphasis>root</emphasis>, 17 18 issue the following commands to add the new user:</para> 19 --> 18 20 19 21 <screen><userinput>groupadd lfs 20 22 useradd -s /bin/bash -g lfs -m -k /dev/null lfs</userinput></screen> 21 23 24 <!-- 22 25 <para>The meaning of the switches:</para> 23 26 … … 53 56 <para>If you want to be able to log in as <emphasis>lfs</emphasis>, then give 54 57 <emphasis>lfs</emphasis> a password:</para> 58 --> 55 59 56 60 <screen><userinput>passwd lfs</userinput></screen> 57 61 62 <!-- 58 63 <para>and grant <emphasis>lfs</emphasis> full access to 59 64 <filename class="directory">$LFS/tools</filename> by making 60 65 <emphasis>lfs</emphasis> the directory owner:</para> 66 --> 61 67 62 68 <screen><userinput>chown lfs $LFS/tools</userinput></screen> 63 69 70 <!-- 64 71 <para>If you made a separate working directory as suggested, give user 65 72 <emphasis>lfs</emphasis> ownership of this directory too:</para> 73 --> 66 74 67 75 <screen><userinput>chown lfs $LFS/sources</userinput></screen> 68 76 77 <!-- 69 78 <para>Next, login as user <emphasis>lfs</emphasis>. This can be done via a 70 79 virtual console, through a display manager, or with the following substitute 71 80 user command:</para> 81 --> 72 82 73 83 <screen><userinput>su - lfs</userinput></screen> 74 84 85 <!-- 75 86 <para>The <quote><parameter>-</parameter></quote> instructs <command>su</command> to 76 87 start a <emphasis>login</emphasis> shell.</para> 88 --> 77 89 78 90 </sect1> -
chapter04/creatingtoolsdir.xml
r86ca6e7 rae79672 8 8 <?dbhtml filename="creatingtoolsdir.html"?> 9 9 10 <!-- 10 11 <para>All programs compiled in <xref linkend="chapter-temporary-tools"/> will be installed under <filename 11 12 class="directory">$LFS/tools</filename> to keep them separate from the … … 21 22 tools are stored. Instead of the simple <quote>tools</quote> you could use 22 23 something like <quote>tools-for-lfs</quote>. However, you'll need to be careful 23 to adjust all references to <quote>tools</quote> throughout the book - -24 to adjust all references to <quote>tools</quote> throughout the book - 24 25 including those in any patches, notably the GCC Specs Patch.</para> 25 26 26 27 <para>Create the required directory by running the following:</para> 28 --> 27 29 28 30 <screen><userinput>mkdir $LFS/tools</userinput></screen> 29 31 32 <!-- 30 33 <para>The next step is to create a <filename>/tools</filename> symlink on 31 34 your <emphasis>host</emphasis> system. It will point to the directory we just created on the LFS 32 35 partition:</para> 36 --> 33 37 34 38 <screen><userinput>ln -s $LFS/tools /</userinput></screen> 35 39 40 <!-- 36 41 <note><para>The above command is correct. The <command>ln</command> command 37 42 has a few syntactic variations, so be sure to check the info page before … … 43 48 from the host) <emphasis>and</emphasis> in the next (when we are <quote>chrooted</quote> to 44 49 the LFS partition).</para> 50 --> 45 51 46 52 </sect1> -
chapter04/settingenviron.xml
r86ca6e7 rae79672 8 8 <?dbhtml filename="settingenvironment.html"?> 9 9 10 <!-- 10 11 <para>We're going to set up a good working environment by creating two new 11 12 startup files for the <command>bash</command> shell. While logged in as 12 13 user <emphasis>lfs</emphasis>, issue the following command to create a new 13 14 <filename>.bash_profile</filename>:</para> 15 --> 14 16 15 17 <screen><userinput>cat > ~/.bash_profile << "EOF" … … 17 19 EOF</userinput></screen> 18 20 21 <!-- 19 22 <para>Normally, when you log on as user <emphasis>lfs</emphasis>, 20 23 the initial shell is a <emphasis>login</emphasis> shell which reads the … … 32 35 <filename>.bash_profile</filename> files, but reads the 33 36 <filename>.bashrc</filename> file instead. Create this latter file now:</para> 37 --> 34 38 35 39 <screen><userinput>cat > ~/.bashrc << "EOF" … … 42 46 EOF</userinput></screen> 43 47 48 <!-- 44 49 <para>The <command>set +h</command> command turns off 45 50 <command>bash</command>'s hash function. Normally hashing is a useful … … 75 80 <para>Finally, to have our environment fully prepared for building the 76 81 temporary tools, source the just-created profile:</para> 82 --> 77 83 78 84 <screen><userinput>source ~/.bash_profile</userinput></screen>
Note:
See TracChangeset
for help on using the changeset viewer.
