- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
part3intro/toolchaintechnotes.xml
r8b539af rb6d3512 301 301 <command>ld</command> by passing it the <parameter>--verbose</parameter> 302 302 flag. For example, <command>$LFS_TGT-ld --verbose | grep SEARCH</command> 303 will illustrate the current search paths and their order. Note that this 304 example can be run as shown only while being user 305 <systemitem class="username">lfs</systemitem>. If you come back to this 306 page later, replace <command>$LFS_TGT-ld</command> with just 307 <command>ld</command>.</para> 303 will illustrate the current search paths and their order. It shows which 304 files are linked by <command>ld</command> by compiling a dummy program and 305 passing the <parameter>--verbose</parameter> switch to the linker. For 306 example, 307 <command>$LFS_TGT-gcc dummy.c -Wl,--verbose 2>&1 | grep succeeded</command> 308 will show all the files successfully opened during the linking.</para> 308 309 309 310 <para>The next package installed is gcc. An example of what can be … … 318 319 operation of <command>gcc</command> itself, the same search paths are not 319 320 necessarily used. To find out which standard linker <command>gcc</command> 320 will use, run: <command>$LFS_TGT-gcc -print-prog-name=ld</command>. Again, 321 remove the <command>$LFS_TGT-</command> part if coming back to this 322 later.</para> 321 will use, run: <command>$LFS_TGT-gcc -print-prog-name=ld</command>.</para> 323 322 324 323 <para>Detailed information can be obtained from <command>gcc</command> by 325 324 passing it the <parameter>-v</parameter> command line option while compiling 326 a program. For example, <command>$LFS_TGT-gcc -v 327 <replaceable>example.c</replaceable></command> (or without <command> 328 $LFS_TGT-</command> if coming back later to this) will show 325 a dummy program. For example, <command>gcc -v dummy.c</command> will show 329 326 detailed information about the preprocessor, compilation, and assembly 330 stages, including <command>gcc</command>'s search paths for included331 headers and theirorder.</para>327 stages, including <command>gcc</command>'s included search paths and their 328 order.</para> 332 329 333 330 <para>Next installed are sanitized Linux API headers. These allow the
Note:
See TracChangeset
for help on using the changeset viewer.