Ignore:
Timestamp:
10/12/2003 01:17:37 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:
a67cde7
Parents:
f27835d
Message:

Minor touchups.

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter05/toolchaintechnotes.xml

    rf27835d ra3f6e124  
    3939<filename class="directory">/lib</filename> directory on your host system. A
    4040surefire way is to inspect a random binary from your host system by running:
    41 <userinput>`readelf -l &lt;name of binary&gt; | grep interpreter`</userinput>
     41<userinput>'readelf -l &lt;name of binary&gt; | grep interpreter'</userinput>
    4242and noting the output. The authoritative reference covering all platforms is in
    4343the <filename>shlib-versions</filename> file in the root of the Glibc source
    … …  
    7676the linker is its library search order. Detailed information can be obtained
    7777from <userinput>ld</userinput> by passing it the <emphasis>--verbose</emphasis>
    78 flag. For example: <userinput>`ld --verbose | grep SEARCH`</userinput> will
     78flag. For example: <userinput>'ld --verbose | grep SEARCH'</userinput> will
    7979show you the current search paths and their order. You can see what files are
    8080actually linked by <userinput>ld</userinput> by compiling a dummy program and
    8181passing the <emphasis>--verbose</emphasis> switch. For example:
    82 <userinput>`gcc dummy.c -Wl,--verbose 2>&amp;1 | grep succeeded`</userinput>
     82<userinput>'gcc dummy.c -Wl,--verbose 2>&amp;1 | grep succeeded'</userinput>
    8383will show you all the files successfully opened during the link.</para>
    8484
    … …  
    9494itself, the same search paths are not necessarily used. You can find out which
    9595standard linker <userinput>gcc</userinput> will use by running:
    96 <userinput>`gcc -print-prog-name=ld`</userinput>.
     96<userinput>'gcc -print-prog-name=ld'</userinput>.
    9797Detailed information can be obtained from <userinput>gcc</userinput> by passing
    9898it the <emphasis>-v</emphasis> flag while compiling a dummy program. For
    99 example: <userinput>`gcc -v dummy.c`</userinput> will show you detailed
     99example: <userinput>'gcc -v dummy.c'</userinput> will show you detailed
    100100information about the preprocessor, compilation and assembly stages, including
    101101<userinput>gcc</userinput>'s include search paths and their order.</para>
    … …  
    127127hard-wired path to a dynamic linker is embedded into every ELF shared
    128128executable. You can inspect this by running:
    129 <userinput>`readelf -l &lt;name of binary&gt; | grep interpreter`</userinput>.
     129<userinput>'readelf -l &lt;name of binary&gt; | grep interpreter'</userinput>.
    130130By amending <userinput>gcc</userinput>'s specs file, we are ensuring that every
    131131program compiled from here through the end of Chapter 5 will use our new
Note: See TracChangeset for help on using the changeset viewer.