Changeset f861982


Ignore:
Timestamp:
10/07/2003 06:00:35 AM (21 years ago)
Author:
Greg Schafer <greg@…>
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
Message:

Miscellaneous fixes and cleanups.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2932 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:
13 edited

Legend:

Unmodified
Added
Removed
  • chapter03/creatingfs.xml

    rf57e3d1 rf861982  
    88systems are becoming increasingly popular. Here we will create an ext2 file
    99system, 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>
     10url="&blfs-root;view/stable/postlfs/filesystems.html"/>.</para>
    1111
    1212<para>To create an ext2 file system on the LFS partition run the following:</para>
  • chapter05/gcc-pass2-inst.xml

    rf57e3d1 rf861982  
    154154
    155155<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>
     156we performed earlier in the chapter. Refer back to
     157<xref linkend="ch05-locking-glibc"/> and repeat the check. If the results are
     158wrong then most likely, you forgot to apply the above mentioned GCC Specs
     159patch.</para></note>
    159160
    160161</sect2>
  • chapter05/glibc-inst.xml

    rf57e3d1 rf861982  
    66<para>Before starting to install Glibc, you must <userinput>cd</userinput>
    77into the <filename>glibc-&glibc-version;</filename> directory and unpack
    8 Glibc-linuxthreads in that directory, not in <filename>/usr/src</filename> as
    9 you would normally do.</para>
     8Glibc-linuxthreads in that directory, not in <filename>$LFS/tools/src</filename>
     9as you would normally do.</para>
    1010
    1111<note><para>We are going to run the test suite for Glibc in this chapter.
  • chapter06/binutils-inst.xml

    rf57e3d1 rf861982  
    5656<para><screen><userinput>make check</userinput></screen></para>
    5757
    58 <para>The test suite notes from the "Installing Binutils - Pass 2" section in
    59 Chapter 5 are still very much appropriate here. Be sure to refer back there
    60 should you have any doubts.</para>
     58<para>The test suite notes from <xref linkend="ch05-binutils-pass2"/> are still
     59very much appropriate here. Be sure to refer back there should you have any
     60doubts.</para>
    6161
    6262<para>Install the package:</para>
  • chapter06/coreutils-inst.xml

    rf57e3d1 rf861982  
    2424<para><screen><userinput>make</userinput></screen></para>
    2525
     26<para>The <userinput>su</userinput> program from Coreutils wasn't installed in
     27Chapter 5 because it needed <emphasis>root</emphasis> privilege to do so. We're
     28going to need it in a few moments for the test suite. Therefore we work around
     29the problem by installing it now:</para>
     30
     31<para><screen><userinput>make install-root</userinput></screen></para>
     32
    2633<para>This package has a test suite available which can perform a number of
    2734checks to ensure it built correctly. However, this particular test suite makes
     
    3542echo "dummy2:x:1001:dummy" >> /etc/group
    3643echo "dummy:x:1000:1000:::/bin/bash" >> /etc/passwd</userinput></screen></para>
    37 
    38 <para>The <userinput>su</userinput> program from Coreutils wasn't installed in
    39 Chapter 5 because it needed <emphasis>root</emphasis> privilege to install. We
    40 work around this problem by installing it now:</para>
    41 
    42 <para><screen><userinput>make install-root</userinput></screen></para>
    4344
    4445<para>Some tests are meant to run as <emphasis>root</emphasis>:</para>
  • chapter06/gcc-2953-inst.xml

    rf57e3d1 rf861982  
    1919<note><para>We don't install the C++ compiler or libraries here. However, there
    2020may 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>
     21at <ulink url="&blfs-root;view/stable/general/gcc2.html"/>.</para></note>
    2222
    2323<para>We'll install this older release of GCC into the non-standard prefix of
  • chapter06/gcc-inst.xml

    rf57e3d1 rf861982  
    1919GCC-testsuite package. The full GCC package contains even more
    2020compilers. 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>
    2222
    2323<para><screen><userinput>patch -Np1 -i ../gcc-&gcc-nofixincludes-patch-version;.patch
     
    5555have any doubts.</para>
    5656
     57<para>The test suite notes from <xref linkend="ch05-gcc-pass2"/> are still very
     58much appropriate here. Be sure to refer back there should you have any
     59doubts.</para>
     60
    5761<para>And install the package:</para>
    5862
     
    7175
    7276<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>
     77we performed earlier in the chapter. Refer back to
     78<xref linkend="ch06-adjustingtoolchain"/> and repeat the check. If the results
     79are wrong then most likely, you erroneously applied the GCC Specs patch from
     80Chapter 5.</para></note>
    7681
    7782</sect2>
  • chapter06/glibc-inst.xml

    rf57e3d1 rf861982  
    5959<para><screen><userinput>make check</userinput></screen></para>
    6060
    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
     62appropriate here. Be sure to refer back there should you have any doubts.</para>
    6463
    6564<para>And install the package:</para>
  • chapter06/grub-inst.xml

    rf57e3d1 rf861982  
    1010Grub.</para>
    1111
    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>
    1413
    1514<para><screen><userinput>patch -Np1 -i ../grub-&grub-patch-version;.patch</userinput></screen></para>
  • chapter06/inetutils-inst.xml

    rf57e3d1 rf861982  
    3333are insecure by nature and are only considered safe on trusted networks. More
    3434information can be found at
    35 <ulink url="&blfs-root;view/cvs/basicnet/inetutils.html"/>. Note that better
     35<ulink url="&blfs-root;view/stable/basicnet/inetutils.html"/>. Note that better
    3636replacements are available for many of these servers.</para></listitem>
    3737</itemizedlist>
  • chapter06/revisedchroot.xml

    rf57e3d1 rf861982  
    66it, you should run the following modified chroot command.</para>
    77
    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
     9a need for the <filename class="directory">/tools</filename> directory. You may
     10delete it. This will also remove the temporary copies of Tcl, Expect and
     11DejaGnu, which were used for running tests on the software as it was built. If
     12you want to use these programs later, you will need to compile and install them
     13on your new LFS system.</para>
    1314
    1415<para><screen><userinput>chroot $LFS /usr/bin/env -i \
  • chapter06/sysvinit-inst.xml

    rf57e3d1 rf861982  
    99to imply that init is sending these signals to all the currently running
    1010processes. To avoid this confusion, the init.c file can be modified, so
    11 that the sentence reads "Sending processes started by init the TERM
    12 signal".</para>
     11that the sentence reads "Sending the TERM signal to processes started by
     12init".</para>
    1313
    1414<para>Edit the halt message:</para>
    1515
    1616<para><screen><userinput>cp src/init.c{,.backup}
    17 sed 's/Sending processes/Sending processes started by init/g' \
     17sed 's/Sending processes/Sending the TERM signal to processes started by init/g' \
    1818&nbsp;&nbsp;&nbsp;&nbsp;src/init.c.backup &gt; src/init.c</userinput></screen></para>
    1919
  • chapter06/vim.xml

    rf57e3d1 rf861982  
    1010
    1111<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"/> for
     12have a look at <ulink url="&blfs-root;view/stable/postlfs/editors.html"/> for
    1313suggested installation instructions.</para>
    1414
Note: See TracChangeset for help on using the changeset viewer.