Changeset 76d113f


Ignore:
Timestamp:
09/21/2003 03:05:40 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:
ebd8ee2
Parents:
dc19fb6
Message:

Toolchain related textual adjustments.

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

Files:
2 edited

Legend:

Unmodified
Added
Removed
  • chapter05/gcc-pass2-inst.xml

    rdc19fb6 r76d113f  
    3636
    3737<para>The last patch changes GCC's default location of the dynamic linker
    38 (typically ld-linux.so.2). It also removes <filename class="directory">/usr/include
    39 </filename> from GCC's include search path. Patching now rather than adjusting
    40 the specs file after installation ensures that our new dynamic linker gets used
    41 during the actual build of GCC. That is, all the final (and temporary) binaries
    42 created during the build will link against the new Glibc.</para>
     38(typically <filename>ld-linux.so.2</filename>). It also removes
     39<filename class="directory">/usr/include</filename> from GCC's include search
     40path. Patching now rather than adjusting the specs file after installation
     41ensures that our new dynamic linker gets used during the actual build of GCC.
     42That is, all the final (and temporary) binaries created during the build will
     43link against the new Glibc.</para>
     44
     45<important><para>These patches are <emphasis>critical</emphasis> in ensuring a
     46successful overall build. Do not forget to apply them.</para></important>
    4347
    4448<para>Create a separate build directory again:</para>
  • chapter06/adjustingtoolchain.xml

    rdc19fb6 r76d113f  
    3737
    3838<caution><para>It is imperative at this point to stop and ensure that the
    39 basic functionality of the adjusted toolchain is working as expected. We are
    40 going to perform a simple sanity check:</para>
     39basic functions (compiling and linking) of the adjusted toolchain are working
     40as expected. For this we are going to perform a simple sanity check:</para>
    4141
    4242<para><screen><userinput>echo 'main(){}' > dummy.c
     
    4444readelf -l a.out | grep ': /lib'</userinput></screen></para>
    4545
    46 <para>If everything is working correctly, the output of the last command will
    47 be:</para>
     46<para>If everything is working correctly, there should be no errors, and the
     47output of the last command will be:</para>
    4848
    4949<para><screen>[Requesting program interpreter: /lib/ld-linux.so.2]
    5050</screen></para>
    5151
    52 <para>If you did not receive the output as shown above then something is
     52<para>If you did not receive the output as shown above, then something is
    5353seriously wrong. You will need to investigate and retrace your steps to find
    5454out where the problem is and correct it. There is no point in continuing
    55 until this is done. Most likely, something went wrong with the specs file
     55until this is done. Most likely something went wrong with the specs file
    5656amendment above. Note especially that <filename>/lib</filename> now appears as
    5757the prefix of our dynamic linker. Of course, if you are working on a platform
    5858where the name of the dynamic linker is something other than <filename>
    59 ld-linux.so.2</filename> then the output will be slightly different.</para>
     59ld-linux.so.2</filename>, then the output will be slightly different.</para>
    6060
    6161<para>Once you are satisfied that all is well, clean up the test files:</para>
Note: See TracChangeset for help on using the changeset viewer.