- Timestamp:
- 01/26/2004 10:23:41 PM (21 years ago)
- 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, 12.2, 12.2-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_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/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- daaa0941
- Parents:
- f2f5117
- Location:
- chapter05
- Files:
-
- 6 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/binutils-pass2.xml
rf2f5117 r17476c5 55 55 <blockquote><screen>make[1]: *** [check-binutils] Error 2</screen></blockquote> 56 56 57 <para>And install the package:</para> 57 <para>And install the package:</para> 58 58 59 59 <screen><userinput>make install</userinput></screen> -
chapter05/chapter05.xml
rf2f5117 r17476c5 309 309 can damage or even wreck your system. Therefore we recommend that you 310 310 build the packages in this chapter as an unprivileged user. You could 311 of course use your own user name, 311 of course use your own user name, but to make it easier to set up a clean 312 312 work environment we'll create a new user <emphasis>lfs</emphasis> and 313 313 use this one during the installation process. As <emphasis>root</emphasis>, … … 383 383 full pathnames of executable files to avoid searching the PATH time and time 384 384 again to find the same executable. However, we'd like the new tools to be 385 used as soon as they are installed. 385 used as soon as they are installed. By switching off the hash function, our 386 386 "interactive" commands (<userinput>make</userinput>, 387 387 <userinput>patch</userinput>, <userinput>sed</userinput>, … … 401 401 having LC_ALL set to something other than "POSIX" or "C" during this chapter 402 402 may cause trouble if you exit the chroot environment and wish to return later. 403 By setting LC_ALL to "POSIX" (or "C", the two are equivalent) 403 By setting LC_ALL to "POSIX" (or "C", the two are equivalent) we ensure that 404 404 everything will work as expected in the chroot environment.</para> 405 405 … … 455 455 456 456 <!-- Ampersands are needed to allow cut and paste --> 457 457 458 458 <screen><userinput>SPECFILE=/tools/lib/gcc-lib/*/*/specs && 459 459 sed -e 's@ /lib/ld-linux.so.2@ /tools/lib/ld-linux.so.2@g' \ … … 477 477 system have found their way into GCC's private include dir. This can happen 478 478 because of GCC's "fixincludes" process which runs as part of the GCC build. 479 We'll explain more about this further on in this chapter. 479 We'll explain more about this further on in this chapter. For now, run the 480 480 following commands to eliminate this possibility:</para> 481 481 -
chapter05/gcc-pass1.xml
rf2f5117 r17476c5 41 41 42 42 <itemizedlist> 43 <listitem><para><userinput>--with-local-prefix=/tools</userinput>: 43 <listitem><para><userinput>--with-local-prefix=/tools</userinput>: The 44 44 purpose of this switch is to remove <filename>/usr/local/include</filename> 45 45 from <userinput>gcc</userinput>'s include search path. This is not absolutely -
chapter05/gcc-pass2.xml
rf2f5117 r17476c5 45 45 patch -Np1 -i ../&gcc-specs-patch;</userinput></screen> 46 46 47 <para>The first patch disables the GCC "fixincludes" script. 47 <para>The first patch disables the GCC "fixincludes" script. We mentioned this 48 48 briefly earlier, but a slightly more in-depth explanation of the fixincludes 49 process is warranted here. 50 script scans your system for header files that need to be fixed. 49 process is warranted here. Under normal circumstances, the GCC fixincludes 50 script scans your system for header files that need to be fixed. It might find 51 51 that some Glibc header files on your host system need to be fixed, fix them and 52 put them in the GCC private include directory. 52 put them in the GCC private include directory. Then, later on in 53 53 <xref linkend="chapter06"/>, after we've installed the newer Glibc, this 54 54 private include directory would be searched before the system include … … 160 160 to continue on.</para> 161 161 162 <para>And finally install the package:</para> 162 <para>And finally install the package:</para> 163 163 164 164 <screen><userinput>make install</userinput></screen> -
chapter05/grep.xml
rf2f5117 r17476c5 24 24 <listitem><para><userinput>--disable-perl-regexp</userinput>: This makes sure 25 25 that <userinput>grep</userinput> does not get linked against a PCRE library 26 that may be present on the host , butwould not be available once we enter the26 that may be present on the host and would not be available once we enter the 27 27 chroot environment.</para></listitem> 28 28 <listitem><para><userinput>--with-included-regex</userinput>: This ensures that 29 Grep uses its internal regular expression code. Without it, it will use30 the code from Glibc, which is known to be slightly buggy.</para></listitem>29 Grep uses its internal regular expression code. Without this switch, Grep will 30 use the code from Glibc, which is known to be slightly buggy.</para></listitem> 31 31 </itemizedlist> 32 32 -
chapter05/utillinux.xml
rf2f5117 r17476c5 15 15 16 16 <para>Util-linux doesn't use the freshly installed headers and libraries from 17 the <filename>/tools</filename> directory. 17 the <filename>/tools</filename> directory. This is fixed by altering the 18 18 configure script:</para> 19 19
Note:
See TracChangeset
for help on using the changeset viewer.