- Timestamp:
- 09/20/2002 09:11:28 PM (22 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, v4_0, v4_1, v5_0, 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:
- 88abb11
- Parents:
- eb7df24
- Location:
- chapter05
- Files:
-
- 9 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/bash-exp.xml
reb7df24 r26e62aa 15 15 <para>It is not strictly necessary for the static bash to be linked 16 16 against libncurses (it can link against a static termcap for the time 17 being just fine because we will reinstall Bash in chapter 6 anyways,17 being just fine because we will reinstall Bash in Chapter 6 anyways, 18 18 where we will use libncurses), but it's a good test to make sure that 19 19 the Ncurses package has been installed properly. If not, you will get in -
chapter05/bash-inst.xml
reb7df24 r26e62aa 43 43 old version of the texinfo package. This error is not severe by any means: the 44 44 info pages will be installed when we recompile bash dynamically in 45 chapter 6, so you can ignore it.</para>45 Chapter 6, so you can ignore it.</para> 46 46 47 47 </sect2> -
chapter05/creatingstaticdir.xml
reb7df24 r26e62aa 12 12 <para><screen><userinput>mkdir $LFS/static</userinput></screen></para> 13 13 14 <para>You may want to move the packages you downloaded in chapter 3 to this14 <para>You may want to move the packages you downloaded in Chapter 3 to this 15 15 <filename class="directory">$LFS/static</filename> directory, perhaps 16 16 create a subdirectory <filename -
chapter05/fileutils-exp.xml
reb7df24 r26e62aa 5 5 glibc 2.2.3 systems. If this isn't done, then there is the possibility of 6 6 all of the fileutils programs causing segmentation faults once chroot is 7 entered in chapter 6.</para>7 entered in Chapter 6.</para> 8 8 9 9 </sect2> -
chapter05/gcc-exp.xml
reb7df24 r26e62aa 13 13 14 14 <para><userinput>--enable-languages=c:</userinput> This builds the C 15 compiler. The C++ compiler will be built in chapter 6, when we rebuild15 compiler. The C++ compiler will be built in Chapter 6, when we rebuild 16 16 GCC. Other compilers are available as well. If they are needed, 17 17 the --enable-languages parameter may be omitted.</para> 18 19 <para><userinput>--enable-threads=posix:</userinput> This enables C++20 exception handling for multithreaded code.</para>21 18 22 19 <para><userinput>echo "#define HAVE_GAS_HIDDEN 1":</userinput> -
chapter05/gcc-inst.xml
reb7df24 r26e62aa 19 19 cd ../gcc-build && 20 20 ../gcc-&gcc-version;/configure --prefix=/static --enable-languages=c \ 21 --disable-nls --disable-shared --enable-threads=posix&&21 --disable-nls --disable-shared && 22 22 echo "#define HAVE_GAS_HIDDEN 1" >> gcc/auto-host.h && 23 23 make BOOT_LDFLAGS=-static bootstrap && -
chapter05/installasuser.xml
reb7df24 r26e62aa 3 3 <?dbhtml filename="installasuser.html" dir="chapter05"?> 4 4 5 <para>When you are logged in as root during chapter 5, it is possible5 <para>When you are logged in as root during Chapter 5, it is possible 6 6 that some files of your host system will be overwritten by the ones 7 you'll build in chapter 5. There can be all kinds of reasons for this7 you'll build in Chapter 5. There can be all kinds of reasons for this 8 8 to happen, for example because the $LFS environment variable is not 9 9 set. Overwriting some files from your host system will most likely 10 10 cause all kinds of problems, so it's a good idea to be logged in as 11 an unprivileged user during chapter 5. To make sure the environment11 an unprivileged user during Chapter 5. To make sure the environment 12 12 is as clean as possible, we'll create a new user "lfs" that can be 13 13 used while building the static installation. Issuing the following … … 47 47 <para>When your host distribution uses a glibc version older than 2.2.4, 48 48 having $LC_ALL set to something else than "C" or "POSIX" while working 49 through chapter 5 may cause trouble when you exit the chroot environment50 of chapter 6 and try to return to it. By setting this to "POSIX" ("C"49 through Chapter 5 may cause trouble when you exit the chroot environment 50 of Chapter 6 and try to return to it. By setting this to "POSIX" ("C" 51 51 is an alias for "POSIX") we ensure that everything will work as expected 52 52 in the chroot environment.</para> -
chapter05/shellutils-inst.xml
reb7df24 r26e62aa 25 25 <para>You can safely ignore that warning. You need to be logged in as root 26 26 in order to install su the way Sh-utils wants to install it, which is being 27 suid root. Because we don't need su during chapter 6, and su will be properly28 installed when we re-install Sh-utils in chapter 6, you can just27 suid root. Because we don't need su during Chapter 6, and su will be properly 28 installed when we re-install Sh-utils in Chapter 6, you can just 29 29 pretend you didn't see it.</para> 30 30 -
chapter05/whystatic.xml
reb7df24 r26e62aa 47 47 <userinput>--disable-shared</userinput>, and 48 48 <userinput>-static</userinput> flags used 49 through chapter 5. Once in chapter 6, the first thing we do is build the49 through Chapter 5. Once in Chapter 6, the first thing we do is build the 50 50 main set of system libraries, glibc. Once this is made we start rebuilding 51 all the programs we just did in chapter 5, but this time dynamically linked,51 all the programs we just did in Chapter 5, but this time dynamically linked, 52 52 so that we can take advantage of the space saving opportunities.</para> 53 53
Note:
See TracChangeset
for help on using the changeset viewer.