Changeset fccdaa1 for part3intro/toolchaintechnotes.xml
- Timestamp:
- 08/18/2024 12:42:43 PM (5 weeks ago)
- Branches:
- xry111/arm64
- Children:
- 8467fab
- Parents:
- 131799a (diff), fcbbf46 (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
r131799a rfccdaa1 193 193 random binary from the host system by running: <userinput>readelf -l 194 194 <name of binary> | grep interpreter</userinput> and noting the 195 output. The authoritative reference covering all platforms is in the196 < filename>shlib-versions</filename> file in the root of the glibc source197 tree.</para>195 output. The authoritative reference covering all platforms is in 196 <ulink url='https://sourceware.org/glibc/wiki/ABIList'>a Glibc wiki 197 page</ulink>.</para> 198 198 </note> 199 199 … … 360 360 <para>Next comes glibc. The most important 361 361 considerations for building glibc are the compiler, binary tools, and 362 kernel headers. The compiler is generally not an issue since glibc will363 always use the compilerrelating to the <parameter>--host</parameter>362 kernel headers. The compiler and binary tools are generally not an issue 363 since glibc will always those relating to the <parameter>--host</parameter> 364 364 parameter passed to its configure script; e.g., in our case, the compiler 365 will be <command>$LFS_TGT-gcc</command>. The binary tools and kernel 366 headers can be a bit more complicated. Therefore, we take no risks and use 367 the available configure switches to enforce the correct selections. After 365 will be <command>$LFS_TGT-gcc</command> and the <command>readelf</command> 366 tool will be <command>$LFS_TGT-readelf</command>. The kernel headers can 367 be a bit more complicated. Therefore, we take no risks and use 368 the available configure switch to enforce the correct selection. After 368 369 the run of <command>configure</command>, check the contents of the 369 370 <filename>config.make</filename> file in the <filename 370 371 class="directory">build</filename> directory for all important details. 371 Note the use of <parameter>CC="$LFS_TGT-gcc"</parameter> (with 372 <envar>$LFS_TGT</envar> expanded) to control which binary tools are used 373 and the use of the <parameter>-nostdinc</parameter> and 374 <parameter>-isystem</parameter> flags to control the compiler's include 375 search path. These items highlight an important aspect of the glibc 372 These items highlight an important aspect of the glibc 376 373 package—it is very self-sufficient in terms of its build machinery, 377 374 and generally does not rely on toolchain defaults.</para>
Note:
See TracChangeset
for help on using the changeset viewer.