- Timestamp:
- 01/27/2003 09:28:02 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, 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_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:
- 8f8e328c
- Parents:
- c118e6c
- Location:
- chapter05
- Files:
-
- 6 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/bash-inst.xml
rc118e6c r558cb8a 16 16 two files again. Often the <filename>libcurses.a</filename> file is (still) 17 17 missing. If so, create <filename>libcurses.a</filename> as a symlink 18 by running the following command sas user <emphasis>root:</emphasis></para>18 by running the following command as user <emphasis>root:</emphasis></para> 19 19 20 20 <para><screen><userinput>ln -s libncurses.a /usr/lib/libcurses.a</userinput></screen></para> … … 51 51 the Ncurses package has been installed properly. If not, you will get in 52 52 trouble later on in this chapter when you install the Texinfo package. 53 That package requires ncurses, and termcap can't reliablybe used53 That package requires ncurses, and termcap can't be used 54 54 there.</para></listitem> 55 55 </itemizedlist> -
chapter05/binutils-inst.xml
rc118e6c r558cb8a 8 8 best left alone. Therefore, if you have defined any environment variables 9 9 that override default optimizations, such as CFLAGS and CXXFLAGS, we 10 recommend unsetting or modifying them when building binutils. You have been 11 warned.</para> 10 recommend unsetting or modifying them when building binutils.</para> 12 11 13 12 <para>It is recommended by the Binutils installation documentation to build -
chapter05/diffutils-inst.xml
rc118e6c r558cb8a 14 14 <listitem><para><userinput>LDFLAGS="-static":</userinput> This is the most 15 15 common way to tell a package that all programs should be statically linked. 16 This way the <emphasis>LDFLAGS</emphasis> environment variable is set but16 This way the <emphasis>LDFLAGS</emphasis> environment variable is set, but 17 17 only in the subshell that the <filename>configure</filename> script runs 18 18 in. When <userinput>configure</userinput> has done its job, the 19 <emphasis>LDFLAGS</emphasis> variable won't exist 20 anymore.</para></listitem> 19 <emphasis>LDFLAGS</emphasis> environment variable won't exist anymore 20 and the <filename>Makefile</filename> files contain will contain this 21 variable locally.</para></listitem> 21 22 22 23 <listitem><para><userinput>CPPFLAGS=-Dre_max_failures=re_max_failures2:</userinput> -
chapter05/fileutils-inst.xml
rc118e6c r558cb8a 16 16 to remove the fileutils-&fileutils-version; directory and unpack it again 17 17 from the tarball before continuing. We believe this may be the case when 18 your distribution has altered Glibc-2.2.3 somehow, but details are19 unavailable at this time.</para>18 your distribution has altered Glibc-2.2.3 somehow, but the exact details 19 are unknown.</para> 20 20 21 21 <para>To fix this package to compile properly on AMD/Glibc-2.2.3 22 22 machines, run the following command. Do <emphasis>NOT</emphasis> 23 23 attempt this fix if you don't have Glibc-2.2.3 installed. It will more 24 than likely result in all kinds of compil e timeproblems.</para>24 than likely result in all kinds of compilation problems.</para> 25 25 26 26 <para><screen><userinput>patch -Np1 -i ../fileutils-&fileutils-patch-version;.patch</userinput></screen></para> -
chapter05/gcc-inst.xml
rc118e6c r558cb8a 11 11 best left alone. Therefore, if you have defined any environment variables 12 12 that override default optimizations, such as CFLAGS and CXXFLAGS, we 13 recommend unsetting or modifying them when building GCC. You have 14 been warned.</para> 13 recommend unsetting or modifying them when building GCC.</para> 15 14 16 15 <para>It is recommended by the GCC installation documentation to build … … 33 32 typo. GCC hard codes some paths while compiling and so we need to pass 34 33 <filename class="directory">/static</filename> as the prefix during the 35 configure stage. We pass the real install prefix during the installation 34 configure stage. We will pass the real installation prefix (<filename 35 class="directory">$LFS/static</filename> during the installation 36 36 stage later on.</para></listitem> 37 37 … … 83 83 in chapter 6 you will install Glibc which will put its header files in 84 84 <filename>/usr/include</filename>. Next you will install other programs that 85 use the Glibc headers .GCC will look in85 use the Glibc headers and GCC will look in 86 86 <filename>/static/lib/gcc-lib</filename> before looking in 87 87 <filename>/usr/include</filename>, with the result of finding and using the -
chapter05/shellutils-inst.xml
rc118e6c r558cb8a 32 32 in order to install su the way Sh-utils wants to install it, which is being 33 33 suid root. Because we don't need su during Chapter 6, and su will be properly 34 installed when we re-install Sh-utils in Chapter 6, you can just 35 pretend you didn't see it.</para> 34 installed when we re-install Sh-utils in Chapter 6.</para> 36 35 37 36 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.