Changeset f861982
- Timestamp:
- 10/07/2003 06:00:35 AM (21 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.0, 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, v5_0, v5_1, v5_1_1, 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:
- 2f5cae8
- Parents:
- f57e3d1
- Files:
-
- 13 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter03/creatingfs.xml
rf57e3d1 rf861982 8 8 systems are becoming increasingly popular. Here we will create an ext2 file 9 9 system, but build instructions for other file systems can be found at <ulink 10 url=" http://www.linuxfromscratch.org/blfs/view/cvs/postlfs/filesystems.html"/>.</para>10 url="&blfs-root;view/stable/postlfs/filesystems.html"/>.</para> 11 11 12 12 <para>To create an ext2 file system on the LFS partition run the following:</para> -
chapter05/gcc-pass2-inst.xml
rf57e3d1 rf861982 154 154 155 155 <note><para>At this point it is strongly recommended to repeat the sanity check 156 we performed earlier in the chapter. Refer back to the "Locking in" Glibc section 157 and repeat the check. If the results are wrong then most likely, you forgot to 158 apply the above mentioned GCC Specs patch.</para></note> 156 we performed earlier in the chapter. Refer back to 157 <xref linkend="ch05-locking-glibc"/> and repeat the check. If the results are 158 wrong then most likely, you forgot to apply the above mentioned GCC Specs 159 patch.</para></note> 159 160 160 161 </sect2> -
chapter05/glibc-inst.xml
rf57e3d1 rf861982 6 6 <para>Before starting to install Glibc, you must <userinput>cd</userinput> 7 7 into the <filename>glibc-&glibc-version;</filename> directory and unpack 8 Glibc-linuxthreads in that directory, not in <filename> /usr/src</filename> as9 you would normally do.</para>8 Glibc-linuxthreads in that directory, not in <filename>$LFS/tools/src</filename> 9 as you would normally do.</para> 10 10 11 11 <note><para>We are going to run the test suite for Glibc in this chapter. -
chapter06/binutils-inst.xml
rf57e3d1 rf861982 56 56 <para><screen><userinput>make check</userinput></screen></para> 57 57 58 <para>The test suite notes from the "Installing Binutils - Pass 2" section in59 Chapter 5 are still very much appropriate here. Be sure to refer back there 60 should you have anydoubts.</para>58 <para>The test suite notes from <xref linkend="ch05-binutils-pass2"/> are still 59 very much appropriate here. Be sure to refer back there should you have any 60 doubts.</para> 61 61 62 62 <para>Install the package:</para> -
chapter06/coreutils-inst.xml
rf57e3d1 rf861982 24 24 <para><screen><userinput>make</userinput></screen></para> 25 25 26 <para>The <userinput>su</userinput> program from Coreutils wasn't installed in 27 Chapter 5 because it needed <emphasis>root</emphasis> privilege to do so. We're 28 going to need it in a few moments for the test suite. Therefore we work around 29 the problem by installing it now:</para> 30 31 <para><screen><userinput>make install-root</userinput></screen></para> 32 26 33 <para>This package has a test suite available which can perform a number of 27 34 checks to ensure it built correctly. However, this particular test suite makes … … 35 42 echo "dummy2:x:1001:dummy" >> /etc/group 36 43 echo "dummy:x:1000:1000:::/bin/bash" >> /etc/passwd</userinput></screen></para> 37 38 <para>The <userinput>su</userinput> program from Coreutils wasn't installed in39 Chapter 5 because it needed <emphasis>root</emphasis> privilege to install. We40 work around this problem by installing it now:</para>41 42 <para><screen><userinput>make install-root</userinput></screen></para>43 44 44 45 <para>Some tests are meant to run as <emphasis>root</emphasis>:</para> -
chapter06/gcc-2953-inst.xml
rf57e3d1 rf861982 19 19 <note><para>We don't install the C++ compiler or libraries here. However, there 20 20 may be reasons why you would want to install them. More information can be found 21 at <ulink url="&blfs-root;view/ cvs/general/gcc2.html"/>.</para></note>21 at <ulink url="&blfs-root;view/stable/general/gcc2.html"/>.</para></note> 22 22 23 23 <para>We'll install this older release of GCC into the non-standard prefix of -
chapter06/gcc-inst.xml
rf57e3d1 rf861982 19 19 GCC-testsuite package. The full GCC package contains even more 20 20 compilers. Instructions for building these can be found at 21 <ulink url="&blfs-root;view/ cvs/general/gcc.html"/>.</para>21 <ulink url="&blfs-root;view/stable/general/gcc.html"/>.</para> 22 22 23 23 <para><screen><userinput>patch -Np1 -i ../gcc-&gcc-nofixincludes-patch-version;.patch … … 55 55 have any doubts.</para> 56 56 57 <para>The test suite notes from <xref linkend="ch05-gcc-pass2"/> are still very 58 much appropriate here. Be sure to refer back there should you have any 59 doubts.</para> 60 57 61 <para>And install the package:</para> 58 62 … … 71 75 72 76 <note><para>At this point it is strongly recommended to repeat the sanity check 73 we performed earlier in the chapter. Refer back to the "Re-adjusting the 74 toolchain" section and repeat the check. If the results are wrong then most 75 likely, you erroneously applied the GCC Specs patch from Chapter 5.</para></note> 77 we performed earlier in the chapter. Refer back to 78 <xref linkend="ch06-adjustingtoolchain"/> and repeat the check. If the results 79 are wrong then most likely, you erroneously applied the GCC Specs patch from 80 Chapter 5.</para></note> 76 81 77 82 </sect2> -
chapter06/glibc-inst.xml
rf57e3d1 rf861982 59 59 <para><screen><userinput>make check</userinput></screen></para> 60 60 61 <para>The test suite notes from the "Installing Glibc" section in Chapter 5 are 62 still very much appropriate here. Be sure to refer back there should you have 63 any doubts.</para> 61 <para>The test suite notes from <xref linkend="ch05-glibc"/> are still very much 62 appropriate here. Be sure to refer back there should you have any doubts.</para> 64 63 65 64 <para>And install the package:</para> -
chapter06/grub-inst.xml
rf57e3d1 rf861982 10 10 Grub.</para> 11 11 12 <para>Grub needs a patch applied that fixes a compile problem with 13 GCC-3.3.1:</para> 12 <para>Grub needs a patch to fix a compilation problem with GCC-3.3.1</para> 14 13 15 14 <para><screen><userinput>patch -Np1 -i ../grub-&grub-patch-version;.patch</userinput></screen></para> -
chapter06/inetutils-inst.xml
rf57e3d1 rf861982 33 33 are insecure by nature and are only considered safe on trusted networks. More 34 34 information can be found at 35 <ulink url="&blfs-root;view/ cvs/basicnet/inetutils.html"/>. Note that better35 <ulink url="&blfs-root;view/stable/basicnet/inetutils.html"/>. Note that better 36 36 replacements are available for many of these servers.</para></listitem> 37 37 </itemizedlist> -
chapter06/revisedchroot.xml
rf57e3d1 rf861982 6 6 it, you should run the following modified chroot command.</para> 7 7 8 <para>Additionally, now that all software has been installed there is no 9 need to use anything from the <filename 10 class="directory">/tools</filename> directory anymore, so it may be deleted. 11 However, since the Tcl, Expect, and DejaGnu packages only exist here, you 12 may want to reinstall them after removing that directory.</para> 8 <para>Additionally, now that all software has been installed, there is no longer 9 a need for the <filename class="directory">/tools</filename> directory. You may 10 delete it. This will also remove the temporary copies of Tcl, Expect and 11 DejaGnu, which were used for running tests on the software as it was built. If 12 you want to use these programs later, you will need to compile and install them 13 on your new LFS system.</para> 13 14 14 15 <para><screen><userinput>chroot $LFS /usr/bin/env -i \ -
chapter06/sysvinit-inst.xml
rf57e3d1 rf861982 9 9 to imply that init is sending these signals to all the currently running 10 10 processes. To avoid this confusion, the init.c file can be modified, so 11 that the sentence reads "Sending processes started by init the TERM12 signal".</para>11 that the sentence reads "Sending the TERM signal to processes started by 12 init".</para> 13 13 14 14 <para>Edit the halt message:</para> 15 15 16 16 <para><screen><userinput>cp src/init.c{,.backup} 17 sed 's/Sending processes/Sending processes started by init/g' \17 sed 's/Sending processes/Sending the TERM signal to processes started by init/g' \ 18 18 src/init.c.backup > src/init.c</userinput></screen></para> 19 19 -
chapter06/vim.xml
rf57e3d1 rf861982 10 10 11 11 <para>If you prefer another editor -- like Emacs, Joe, or Nano -- to Vim, 12 have a look at <ulink url="&blfs-root;view/ cvs/postlfs/editors.html"/> for12 have a look at <ulink url="&blfs-root;view/stable/postlfs/editors.html"/> for 13 13 suggested installation instructions.</para> 14 14
Note:
See TracChangeset
for help on using the changeset viewer.