Changeset 17476c5 for chapter05/chapter05.xml
- Timestamp:
- 01/26/2004 10:23:41 PM (20 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, 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/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- daaa0941
- Parents:
- f2f5117
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
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
Note:
See TracChangeset
for help on using the changeset viewer.