Changeset 8b539af

Timestamp:

10/09/2022 04:46:28 PM (8 months ago)

Author:

Pierre Labastie <pierre.labastie@…>

Branches:

11.3, 11.3-rc1, bdubbs/gcc13, multilib, trunk, xry111/arm64, xry111/clfs-ng, xry111/glibc-2.37, xry111/kcfg-revise, xry111/pip3, xry111/rust-wip-20221008

Children:

32f686f, 44e2a04, 6e24d20

Parents:

312d536

Message:

First attempt at clarifying "Important Preliminary Material"

File:

• part3intro/toolchaintechnotes.xml (modified) (2 diffs)

part3intro/toolchaintechnotes.xml

@@ -301 +301 @@
     <command>ld</command> by passing it the <parameter>--verbose</parameter>
     flag. For example, <command>$LFS_TGT-ld --verbose | grep SEARCH</command>
-    will illustrate the current search paths and their order. It shows which
-    files are linked by <command>ld</command> by compiling a dummy program and
-    passing the <parameter>--verbose</parameter> switch to the linker. For
-    example,
-    <command>$LFS_TGT-gcc dummy.c -Wl,--verbose 2&gt;&amp;1 | grep succeeded</command>
-    will show all the files successfully opened during the linking.</para>
+    will illustrate the current search paths and their order. Note that this
+    example can be run as shown only while being user
+    <systemitem class="username">lfs</systemitem>. If you come back to this
+    page later, replace <command>$LFS_TGT-ld</command> with just
+    <command>ld</command>.</para>
 
     <para>The next package installed is gcc. An example of what can be
@@ -319 +318 @@
     operation of <command>gcc</command> itself, the same search paths are not
     necessarily used. To find out which standard linker <command>gcc</command>
-    will use, run: <command>$LFS_TGT-gcc -print-prog-name=ld</command>.</para>
+    will use, run: <command>$LFS_TGT-gcc -print-prog-name=ld</command>. Again,
+    remove the <command>$LFS_TGT-</command> part if coming back to this
+    later.</para>
 
     <para>Detailed information can be obtained from <command>gcc</command> by
     passing it the <parameter>-v</parameter> command line option while compiling
-    a dummy program. For example, <command>gcc -v dummy.c</command> will show
+    a program. For example, <command>$LFS_TGT-gcc -v
+    <replaceable>example.c</replaceable></command> (or without <command>
+    $LFS_TGT-</command> if coming back later to this) will show
     detailed information about the preprocessor, compilation, and assembly
-    stages, including <command>gcc</command>'s included search paths and their
-    order.</para>
+    stages, including <command>gcc</command>'s search paths for included
+    headers and their order.</para>
 
     <para>Next installed are sanitized Linux API headers. These allow the