Changeset cdc04a1 for part3intro/toolchaintechnotes.xml
- Timestamp:
- 10/18/2022 08:31:34 AM (19 months ago)
- Branches:
- xry111/arm64, xry111/arm64-12.0
- Children:
- 2dc81d4
- Parents:
- 04ca2a7 (diff), 0f9c02a (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
part3intro/toolchaintechnotes.xml
r04ca2a7 rcdc04a1 268 268 should be same as the content of the same package installed in 269 269 &ch-final;. The temporary packages installed in &ch-tmp-cross; or 270 &ch-tmp-chroot; cannot satis ify this expectation because some of them270 &ch-tmp-chroot; cannot satisfy this expectation because some of them 271 271 are built without optional dependencies installed, and autoconf cannot 272 272 perform some feature checks in &ch-tmp-cross; because of cross … … 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. 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> 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> 309 308 310 309 <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 320 319 necessarily used. To find out which standard linker <command>gcc</command> 321 will use, run: <command>$LFS_TGT-gcc -print-prog-name=ld</command>.</para> 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> 322 323 323 324 <para>Detailed information can be obtained from <command>gcc</command> by 324 325 passing it the <parameter>-v</parameter> command line option while compiling 325 a dummy program. For example, <command>gcc -v dummy.c</command> will show 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 326 329 detailed information about the preprocessor, compilation, and assembly 327 stages, including <command>gcc</command>'s included search paths and their328 order.</para>330 stages, including <command>gcc</command>'s search paths for included 331 headers and their order.</para> 329 332 330 333 <para>Next installed are sanitized Linux API headers. These allow the
Note:
See TracChangeset
for help on using the changeset viewer.