Ignore:
Timestamp:
06/12/2020 04:40:07 AM (4 years ago)
Author:
Bruce Dubbs <bdubbs@…>
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, 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:
26fec27
Parents:
ea7ec72
Message:

Mostly text updates in Chapter 8.
There are a couple of minor command changes.

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/cross2@11924 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter08/adjusting.xml

    rea7ec72 r6a156bab  
    5151  <para os="b">There should be no errors,
    5252  and the output of the last command will be (allowing for
    53   platform-specific differences in dynamic linker name):</para>
     53  platform-specific differences in the dynamic linker name):</para>
    5454
    5555<screen os="c"><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
     
    105105<screen os="o"><computeroutput>attempt to open /lib/libc.so.6 succeeded</computeroutput></screen>
    106106
    107   <para os="p">Lastly, make sure GCC is using the correct dynamic linker:</para>
     107  <para os="p">Make sure GCC is using the correct dynamic linker:</para>
    108108
    109109<screen os="q"><userinput>grep found dummy.log</userinput></screen>
     
    116116  <para os="t">If the output does not appear as shown above or is not received
    117117  at all, then something is seriously wrong. Investigate and retrace the
    118   steps to find out where the problem is and correct it. The most likely
    119   reason is that something went wrong with the specs file adjustment. Any
     118  steps to find out where the problem is and correct it. <!--The most likely
     119  reason is that something went wrong with the specs file adjustment.--> Any
    120120  issues will need to be resolved before continuing with the process.</para>
    121121
Note: See TracChangeset for help on using the changeset viewer.