Changeset ede9b9b
- Timestamp:
- 02/25/2004 10:04:14 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:
- dd3e8c6
- Parents:
- e421d2e
- Files:
-
- 13 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
re421d2e rede9b9b 18 18 <listitem><para>man-pages-1.66</para></listitem> 19 19 <listitem><para>ncurses-5.4</para></listitem> 20 </itemizedlist></listitem> 20 </itemizedlist> 21 </listitem> 22 23 <listitem><para>Added:</para> 24 <itemizedlist> 25 <listitem><para>make_devices-1.2</para></listitem> 26 </itemizedlist> 27 </listitem> 28 29 <listitem><para>Removed:</para> 30 <itemizedlist> 31 <listitem><para>MAKEDEV-1.7</para></listitem> 32 <listitem><para>ncurses-5.3-etip-2.patch</para></listitem> 33 </itemizedlist> 34 </listitem> 21 35 22 36 <listitem><para>February 23rd, 2004 [alex]: Chapters 6 + 9 : Cleaned up the -
chapter05/binutils-pass1.xml
re421d2e rede9b9b 18 18 assembler to determine which of their own features to enable.</para> 19 19 20 <para>This package is known to behave badly when you have changedits default21 optimization flags (including the -march and -mcpu options). Therefore, if22 you have defined any environment variables that override default 23 optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting or 24 modifying them when building Binutils.</para>20 <para>This package is known to behave badly when you change its default 21 optimization flags (including the <emphasis>-march</emphasis> and 22 <emphasis>-mcpu</emphasis> options). Therefore, if you have defined any 23 environment variables that override default optimizations, such as CFLAGS and 24 CXXFLAGS, we recommend unsetting them when building Binutils.</para> 25 25 26 26 <para>The Binutils documentation recommends building Binutils outside of the … … 31 31 32 32 <note><para>If you want the SBU values listed in the rest of the book to be of 33 any use, you will have to measure the time it takes to build this package. To 34 achieve this easily, you could do something like: 35 <userinput>time { ./configure ... && ... && ... && make install; }</userinput>.</para></note> 33 any use, you will have to measure the time it takes to build this package -- 34 from the configuration upto and including the first install. To achieve this 35 easily, you could wrap the four commands in a <command>time</command> command 36 like this: <userinput>time { ./configure ... && ... && ... 37 && make install; }</userinput>.</para></note> 36 38 37 39 <para>Now prepare Binutils for compilation:</para> … … 67 69 <listitem><para><userinput>LDFLAGS="-all-static"</userinput>: This tells the 68 70 linker that all the Binutils programs should be linked statically. However, 69 strictly speaking, <emphasis>"-all-static"</emphasis> is firstpassed to the70 <command>libtool</command> program which then passes71 <emphasis>"-static"</emphasis> onto the linker.</para></listitem>71 strictly speaking, <emphasis>"-all-static"</emphasis> is passed to the 72 <command>libtool</command> program, which then passes 73 <emphasis>"-static"</emphasis> to the linker.</para></listitem> 72 74 </itemizedlist> 73 75 74 <para>Compilation is now complete. This is the point where we would normally 75 run the test suite. But as discussed earlier, we don't recommend running the 76 test suites for the temporary tools here in this chapter. However, even if we 77 still wanted to run the Binutils test suite, we're unable do so at this early 78 stage because the test suite framework is not yet in place. Not only that, the 79 programs from this first pass will soon be overwritten by those installed in 80 the second pass.</para> 76 <para>Compilation is complete. Normally we would now run the test suite, but 77 at this early stage the test suite framework (Tcl, Expect and DejaGnu) is not 78 yet in place. And there would be little point in running the tests anyhow, 79 since the programs from this first pass will soon be replaced by those from the 80 second.</para> 81 81 82 82 <para>And install the package:</para> … … 93 93 <itemizedlist> 94 94 <listitem><para><userinput>-C ld clean</userinput>: This tells the make program 95 to remove all the compiled files , but only in the <filename>ld</filename>96 subdirectory.</para></listitem>95 to remove all the compiled files in the <filename 96 class="directory">ld</filename> subdirectory.</para></listitem> 97 97 98 <listitem><para><userinput>-C ld LDFLAGS="-all-static" LIB_PATH=/tools/lib</userinput>:99 This option rebuilds everything in the <filename>ld</filename> subdirectory. 100 Specifying the LIB_PATH makefile variable on the command line allows us to 101 override the default value and have it point to our temporary tools location. 102 The value of this variable specifies the linker's default library search path. 103 You'll see how this preparation is used later on in the 104 chapter.</para></listitem>98 <listitem><para><userinput>-C ld LDFLAGS="-all-static" 99 LIB_PATH=/tools/lib</userinput>: This option rebuilds everything in the 100 <filename class="directory">ld</filename> subdirectory. Specifying the LIB_PATH 101 makefile variable on the command line allows us to override the default value 102 and have it point to our temporary tools location. The value of this variable 103 specifies the linker's default library search path. You will see how this 104 preparation is used later on in the chapter.</para></listitem> 105 105 </itemizedlist> 106 106 -
chapter05/binutils-pass2.xml
re421d2e rede9b9b 8 8 &aa-binutils-down; 9 9 &aa-binutils-dep; 10 11 10 12 11 <sect2><title> </title><para> </para></sect2> … … 29 28 <itemizedlist> 30 29 <listitem><para><userinput>--with-lib-path=/tools/lib</userinput>: This tells 31 the configure script to specify the default library search path. We don't want 32 the library search path to contain library directories from the host 33 system.</para></listitem> 30 the configure script to specify the library search path during the compilation 31 of Binutils, resulting in <emphasis>/tools/lib</emphasis> to be passed to the 32 linker. This prevents the linker from searching through library directories on 33 the host.</para></listitem> 34 34 </itemizedlist> 35 35 … … 42 42 43 43 <para>Compilation is now complete. As discussed earlier, we don't recommend 44 running the test suites for the temporary tools here in this chapter. If you45 still want to run the Binutils test suite anyway, the following command will 46 do so:</para>44 running the test suites for the temporary tools here in this chapter. If 45 nevertheless you want to run the Binutils test suite, the following command 46 will do so:</para> 47 47 48 48 <screen><userinput>make check</userinput></screen> 49 49 50 50 <para>There should be no unexpected failures here, expected failures are fine. 51 Unfortunately, there is no easy way to view the test results summary like 52 there was for the previous GCC package. However, if a failure occurs here, it 53 should be easyto spot. The output shown will contain something like:</para>51 Unfortunately, there is no easy way to view the test results summary like there 52 was for the GCC package. However, if a failure occurs here, it should be easy 53 to spot. The output shown will contain something like:</para> 54 54 55 55 <blockquote><screen>make[1]: *** [check-binutils] Error 2</screen></blockquote> -
chapter05/chapter05.xml
re421d2e rede9b9b 513 513 514 514 <para>If everything is working correctly, there should be no errors, and the 515 output of the last command will be:</para> 515 output of the last command will be (allowing for platform specific differences 516 in dynamic linker name):</para> 516 517 517 518 <blockquote><screen>[Requesting program interpreter: /tools/lib/ld-linux.so.2]</screen></blockquote> 518 519 519 <para>(Of course allowing for platform specific differences in dynamic linker 520 name). Note especially that <filename class="directory">/tools/lib</filename> 521 appears as the prefix of our dynamic linker. If you did not receive the output 520 <para>Note especially that <filename class="directory">/tools/lib</filename> 521 appears as the prefix of our dynamic linker.</para> 522 523 <para>If you did not receive the output 522 524 as shown above, or received no output at all, then something is seriously wrong. 523 525 You will need to investigate and retrace your steps to find out where the -
chapter05/coreutils.xml
re421d2e rede9b9b 18 18 <title>Installation of Coreutils</title> 19 19 20 <para> Coreutilshas an issue when compiled against Glibc-&glibc-version;.21 Without the patch below, some of the Coreutils utilities 22 (<command>head</command>, <command>tail</command> , <command>sort</command>,23 and others) will reject their traditional syntax whichhas been in use for20 <para>This package has an issue when compiled against Glibc-&glibc-version;. 21 Without the patch below, some of the Coreutils utilities (such as 22 (<command>head</command>, <command>tail</command> and <command>sort</command>) 23 will reject their traditional syntax, a syntax that has been in use for 24 24 approximately 30 years. This old syntax is so pervasive that compatibility 25 should be preserved until the many places where it is used can be updated. 26 More details on this are provided in the comments inside the patch itself. Use 27 ofthis patch is by no means compulsory, but not using it means you'll have to28 deal with the consequences yourself: patch the many packages that use the old29 syntax. Therefore, better apply the patch:</para>25 should be preserved until the many places where it is used can be updated. More 26 details on this are provided in the comments inside the patch itself. Use of 27 this patch is by no means compulsory, but not using it means you'll have to 28 deal with the consequences yourself: patch the many packages that still use the 29 old syntax. Therefore, better apply the patch:</para> 30 30 31 31 <screen><userinput>patch -Np1 -i ../&coreutils-posixver-patch;</userinput></screen> -
chapter05/expect.xml
re421d2e rede9b9b 17 17 <title>Installation of Expect</title> 18 18 19 <para>First apply a patch:</para> 19 <para>First fix a bug that can result in bogus failures during the GCC test 20 suite run:</para> 20 21 21 22 <screen><userinput>patch -Np1 -i ../&expect-patch;</userinput></screen> 22 23 <para>This fixes a bug in Expect that can result in bogus failures during the24 GCC test suite run.</para>25 23 26 24 <para>Now prepare Expect for compilation:</para> … … 58 56 59 57 <itemizedlist> 60 <listitem><para><userinput>SCRIPTS=""</userinput>: This prevents installation of61 the supplementary expect scripts which are not needed.</para></listitem>58 <listitem><para><userinput>SCRIPTS=""</userinput>: This prevents installation 59 of the supplementary expect scripts which are not needed.</para></listitem> 62 60 </itemizedlist> 63 61 -
chapter05/gcc-pass1.xml
re421d2e rede9b9b 16 16 <title>Installation of GCC</title> 17 17 18 <para>Unpack only the GCC-core tarball, as we won't be needing aC++ compiler19 forthe moment.</para>18 <para>Unpack only the GCC-core tarball, as we won't be needing the C++ compiler 19 nor the test suite at the moment.</para> 20 20 21 <para>This package is known to behave badly when you have changed its22 default optimization flags (including the -march and -mcpu options). 23 Therefore, if you have defined any environment variables that override 24 default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting 25 or modifying them when building GCC.</para>21 <para>This package is known to behave badly when you change its default 22 optimization flags (including the <emphasis>-march</emphasis> and 23 <emphasis>-mcpu</emphasis> options). Therefore, if you have defined any 24 environment variables that override default optimizations, such as CFLAGS and 25 CXXFLAGS, we recommend unsetting them when building GCC.</para> 26 26 27 27 <para>The GCC documentation recommends building GCC outside of the source … … 53 53 script for Glibc (the next package we compile) produces the proper results. 54 54 Note that the <command>gcc</command> binaries will still be linked 55 statically, as this is controlled by the < command>-static</command>56 value of BOOT_LDFLAGS further on.</para></listitem>55 statically, as this is controlled by the <emphasis>-static</emphasis> 56 value of BOOT_LDFLAGS in the next step.</para></listitem> 57 57 58 58 <listitem><para><userinput>--enable-languages=c</userinput>: This option … … 79 79 </itemizedlist> 80 80 81 <para>Compilation is now complete. This is the point where we would normally 82 run the test suite. But as discussed earlier, we don't recommend running the 83 test suites for the temporary tools here in this chapter. However, even if we 84 still wanted to run the GCC test suite, we're unable do so at this early stage 85 because the test suite framework is not yet in place. Not only that, the 86 programs from this first pass will soon be overwritten by those installed in 87 the second pass.</para> 81 <para>Compilation is now complete, and at this point we would normally run the 82 test suite. But, as mentioned before, the test suite framework is not in place 83 yet. And there would be little point in running the tests anyhow, since the 84 programs from this first pass will soon be replaced.</para> 88 85 89 86 <para>And install the package:</para> … … 91 88 <screen><userinput>make install</userinput></screen> 92 89 93 <para>As a finishing touch we'll create the <filename 94 class="symlink">/tools/bin/cc</filename> symlink. Many programs and 95 scripts run <command>cc</command> instead of <command>gcc</command>, 90 <para>As a finishing touch we'll create a symlink. Many programs and scripts 91 run <command>cc</command> instead of <command>gcc</command>, 96 92 a thing meant to keep programs generic and therefore usable on all kinds of 97 93 Unix systems. Not everybody has the GNU C compiler installed. Simply running -
chapter05/gcc-pass2.xml
re421d2e rede9b9b 14 14 <title>Re-installation of GCC</title> 15 15 16 <para>The tools required to test GCC and Binutils are installed now (Tcl, Expect17 and DejaGnu). We can continue on rebuilding GCC and Binutils, link them against 18 the new Glibc, and test them properly (if performing the test suites in this19 chapter). One thing to note, however, is that these test suites are highly 20 dependent on properly functioning pseudo terminals (PTYs) which are provided by 21 your host distribution. These days, PTYs are most commonly implemented via the16 <para>The tools required to test GCC and Binutils are installed now: Tcl, 17 Expect and DejaGnu. Therefore we can now rebuild GCC and Binutils, linking 18 them against the new Glibc, and test them properly (if running the test suites 19 in this chapter). One thing to note, however, is that these test suites are 20 highly dependent on properly functioning pseudo terminals (PTYs) which are 21 provided by your host. These days, PTYs are most commonly implemented via the 22 22 <emphasis>devpts</emphasis> file system. You can quickly check if your host 23 23 system is set up correctly in this regard by performing a simple test:</para> … … 25 25 <screen><userinput>expect -c "spawn ls"</userinput></screen> 26 26 27 <para> If you receive the message:</para>27 <para>The response might be:</para> 28 28 29 29 <blockquote><screen>The system has no more ptys. Ask your system administrator to create more.</screen></blockquote> 30 30 31 <para> Your host distribution is not set up for proper PTY operation. In this32 case there is no point in running the test suites for GCC and Binutils until 33 you are able to resolve the issue. You can consult the LFS Wiki at 34 <ulink url="&wiki-root;"/> for more information on how to get PTYs31 <para>If you receive the above message, your host doesn't have its PTYs set up 32 properly. In this case there is no point in running the test suites for GCC 33 and Binutils until you are able to resolve the issue. You can consult the LFS 34 Wiki at <ulink url="&wiki-root;"/> for more information on how to get PTYs 35 35 working.</para> 36 36 37 37 <para>This time we will build both the C and the C++ compilers, so you'll have 38 to unpack all three GCC tarballs (-core, -g++, and -testsuite) in one and the39 same working directory. They will all unfold into a single 40 <filename>&gcc-dir;/</filename> subdirectory.</para>38 to unpack both the core and the g++ tarballs (and testsuite too, if you want to 39 run the tests). Unpacking them in your working directory, they will all unfold 40 into a single <filename>&gcc-dir;/</filename> subdirectory.</para> 41 41 42 <para>First correct oneproblem and make an essential adjustment:</para>42 <para>First correct a problem and make an essential adjustment:</para> 43 43 44 44 <screen><userinput>patch -Np1 -i ../&gcc-nofixincludes-patch; … … 57 57 system.</para> 58 58 59 <para>The lastpatch changes GCC's default location of the dynamic linker59 <para>The second patch changes GCC's default location of the dynamic linker 60 60 (typically <filename>ld-linux.so.2</filename>). It also removes 61 61 <filename class="directory">/usr/include</filename> from GCC's include search … … 87 87 88 88 <itemizedlist> 89 <listitem><para><userinput>--enable-clocale=gnu</userinput>: This option 90 ensures the correct locale model is selected for the C++ libraries under all 91 circumstances. If the configure script finds the <emphasis>de_DE</emphasis> 92 locale installed, it will select the correct <emphasis>gnu</emphasis> locale 93 model. However, people who don't install the <emphasis>de_DE</emphasis> locale 94 would run the risk of building ABI incompatible C++ libraries due to the wrong 95 <emphasis>generic</emphasis> locale model being selected.</para></listitem> 96 89 97 <listitem><para><userinput>--enable-threads=posix</userinput>: This enables 90 98 C++ exception handling for multi-threaded code.</para></listitem> … … 97 105 distributions.</para></listitem> 98 106 99 <listitem><para><userinput>--enable-clocale=gnu</userinput>: This option ensures 100 the correct locale model is selected for the C++ libraries under all 101 circumstances. If the configure script finds the <emphasis>de_DE</emphasis> 102 locale installed, it will select the correct model of <emphasis>gnu</emphasis>. 103 However, people who don't install the <emphasis>de_DE</emphasis> locale, run the 104 risk of building ABI incompatible C++ libraries due to the wrong locale model of 105 <emphasis>generic</emphasis> being selected.</para></listitem> 106 107 <listitem><para><userinput>--enable-languages=c,c++</userinput>: This option is 108 needed to ensure that both C and C++ compilers are built.</para></listitem> 107 <listitem><para><userinput>--enable-languages=c,c++</userinput>: This option 108 ensures that both the C and C++ compilers are built.</para></listitem> 109 109 </itemizedlist> 110 110 … … 117 117 version of the GCC sources we used earlier.</para> 118 118 119 <para>Compilation is now complete. As discussed earlier, we don't recommend119 <para>Compilation is now complete. As mentioned earlier, we don't recommend 120 120 running the test suites for the temporary tools here in this chapter. If you 121 121 still want to run the GCC test suite anyway, the following command will do … … 151 151 152 152 <para>The 24 unexpected passes for libstdc++ are due to the use of 153 <emphasis>--enable-clocale=gnu</emphasis>, which is the correct choice on 154 Glibc-based systems of versions 2.2.5 and above. The underlying locale support 155 in the GNU C library is superior to that of the otherwise selected "generic" 156 model (which may be applicable if for instance you were using Newlibc, Sun-libc 157 or whatever libc). The libstdc++ test suite is apparently expecting the 158 "generic" model, hence those tests are not always expected to pass.</para> 153 <emphasis>--enable-clocale=gnu</emphasis>. This option, which is the correct 154 choice on Glibc-based systems of versions 2.2.5 and above, enables in the GNU C 155 library a locale support that is superior to the otherwise selected 156 <emphasis>generic</emphasis> model (which may be applicable if for instance you 157 were using Newlibc, Sun-libc or whatever other libc). The libstdc++ test suite 158 is apparently expecting the <emphasis>generic</emphasis> model, hence those 159 tests are not always expected to pass.</para> 159 160 160 <para> Unexpected failures often cannot be avoided. The GCC developers are161 usually aware of them but haven't yet gotten around to fixing them. In short, 162 unless your results are vastly different from those at the above URL, it is safe163 to continue on.</para>161 <para>Having a few unexpected failures often cannot be avoided. The GCC 162 developers are usually aware of these, but haven't yet gotten around to fixing 163 them. In short, unless your results are vastly different from those at the 164 above URL, it is safe to continue.</para> 164 165 165 166 <para>And finally install the package:</para> … … 169 170 <note><para>At this point it is strongly recommended to repeat the sanity check 170 171 we performed earlier in this chapter. Refer back to 171 <xref linkend="ch-tools-adjusting"/> and repeat the check. If the results are172 wrong, then most likely you forgot to apply the above mentioned GCC Specs 173 patch.</para></note>172 <xref linkend="ch-tools-adjusting"/> and repeat the little test compilation. If 173 the result is wrong, then most likely you forgot to apply the above mentioned 174 GCC Specs patch.</para></note> 174 175 175 176 </sect2> -
chapter05/glibc.xml
re421d2e rede9b9b 14 14 <title>Installation of Glibc</title> 15 15 16 <para>This package is known to behave badly when you have changed its17 default optimization flags (including the -march and -mcpu options). 18 Therefore, if you have defined any environment variables that override 19 default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting 20 them when building Glibc.</para>16 <para>This package is known to behave badly when you change its default 17 optimization flags (including the <emphasis>-march</emphasis> and 18 <emphasis>-mcpu</emphasis> options). Therefore, if you have defined any 19 environment variables that override default optimizations, such as CFLAGS and 20 CXXFLAGS, we recommend unsetting them when building Glibc.</para> 21 21 22 22 <para>Basically, compiling Glibc in any other way than the book suggests … … 41 41 <listitem><para><userinput>--disable-profile</userinput>: This disables the 42 42 building of the libraries with profiling information. Omit this option if you 43 plan to do profiling .</para></listitem>43 plan to do profiling on the temporary tools.</para></listitem> 44 44 45 45 <listitem><para><userinput>--enable-add-ons=linuxthreads</userinput>: This … … 72 72 *** Check the INSTALL file for required versions.</screen></blockquote> 73 73 74 <para>The missing or incompatible < filename>msgfmt</filename> program is74 <para>The missing or incompatible <command>msgfmt</command> program is 75 75 generally harmless, but it's believed it can sometimes cause problems when 76 76 running the test suite.</para> … … 80 80 <screen><userinput>make</userinput></screen> 81 81 82 <para>Compilation is now complete. As discussed earlier, we don't recommend82 <para>Compilation is now complete. As mentioned earlier, we don't recommend 83 83 running the test suites for the temporary system here in this chapter. If you 84 84 still want to run the Glibc test suite anyway, the following command will do … … 91 91 can be adversely affected by existing tools or environmental issues on the host 92 92 system. Of course, these won't be a problem when we run the Glibc test suite 93 inside the chroot environment of <xref linkend="chapter-building-system"/>. In general, the94 Glibc test suite is always expected to pass. However, as mentioned above, some 95 failures are unavoidable in certain circumstances. Here is a list of the most96 common issues we are aware of:</para>93 inside the chroot environment of <xref linkend="chapter-building-system"/>. In 94 general, the Glibc test suite is always expected to pass. However, as mentioned 95 above, in certain circumstances some failures are unavoidable. Here is a list 96 of the most common issues we are aware of:</para> 97 97 98 98 <itemizedlist> … … 118 118 119 119 <para>In summary, don't worry too much if you see Glibc test suite failures 120 here in this chapter. The Glibc in <xref linkend="chapter-building-system"/> is the one we'll 121 ultimately end up using so that is the one we would really like to see pass. 122 But please keep in mind, even in <xref linkend="chapter-building-system"/> some failures 123 could still occur -- the <emphasis>math</emphasis> 124 tests for example. When experiencing a failure, make a note of it, then 125 continue by reissuing the <command>make check</command>. The test suite 126 should pick up where it left off and continue on. You can circumvent this 127 stop-start sequence by issuing a <command>make -k check</command>. But if 128 you do that, be sure to log the output so that you can later peruse the log 129 file and examine the total number of failures.</para> 120 here in this chapter. The Glibc in <xref linkend="chapter-building-system"/> is 121 the one we'll ultimately end up using, so that is the one we would really like 122 to see pass the tests (but even there some failures could still occur -- the 123 <emphasis>math</emphasis> tests, for example). When experiencing a failure, 124 make a note of it, then continue by reissuing the <command>make 125 check</command>. The test suite should pick up where it left off and continue. 126 You can circumvent this stop-start sequence by issuing a <command>make -k 127 check</command>. But if you do that, be sure to log the output so that you can 128 later peruse the log file and examine the total number of failures.</para> 130 129 131 <para>Though it is a harmless message, the install stage of Glibc will 132 complain about the absence of <filename>/tools/etc/ld.so.conf</filename>.133 Fix this annoying little warning with:</para>130 <para>Though it is a harmless message, the install stage of Glibc will at the 131 end complain about the absence of <filename>/tools/etc/ld.so.conf</filename>. 132 Prevent this confusing little warning with:</para> 134 133 135 134 <screen><userinput>mkdir /tools/etc -
chapter05/kernelheaders.xml
re421d2e rede9b9b 20 20 21 21 <para>This ensures that the kernel tree is absolutely clean. The kernel team 22 recommends that this command be issued prior to <emphasis>each</emphasis> kernel23 compilation. You shouldn't rely on the source tree being clean after22 recommends that this command be issued prior to <emphasis>each</emphasis> 23 kernel compilation. You shouldn't rely on the source tree being clean after 24 24 untarring.</para> 25 25 -
chapter05/tcl.xml
re421d2e rede9b9b 16 16 <title>Installation of Tcl</title> 17 17 18 <para>This package and the next two are only installed to be able to run the 19 test suites for GCC and Binutils. Installing three packages just for testing 20 purposes may seem like overkill, but it is very reassuring, if not essential, 18 <para>This package and the next two are only installed to be able to run the 19 test suites for GCC and Binutils. Installing three packages just for testing 20 purposes may seem like overkill, but it is very reassuring, if not essential, 21 21 to know that our most important tools are working properly. Even if you are 22 22 not running the test suites here in this chapter as per our recommendation, 23 these packages are still required for the test suites in the next23 these packages are still required for running the test suites in the next 24 24 chapter.</para> 25 25 -
chapter06/chapter06.xml
re421d2e rede9b9b 437 437 438 438 <para>If everything is working correctly, there should be no errors, and the 439 output of the last command will be:</para> 439 output of the last command will be (allowing for platform specific differences 440 in dynamic linker name):</para> 440 441 441 442 <blockquote><screen>[Requesting program interpreter: /lib/ld-linux.so.2]</screen></blockquote> 442 443 443 <para>(Of course allowing for platform specific differences in dynamic linker 444 name). Note especially that <filename class="directory">/lib</filename> now 445 appears as the prefix of our dynamic linker. If you did not receive the output 444 <para>Note especially that <filename class="directory">/lib</filename> is now 445 the prefix of our dynamic linker.</para> 446 447 <para> If you did not receive the output 446 448 as shown above, or received no output at all, then something is seriously wrong. 447 449 You will need to investigate and retrace your steps to find out where the -
index.xml
re421d2e rede9b9b 3 3 "/usr/share/docbook/docbookx.dtd" [ 4 4 5 <!ENTITY version "CVS-2004-02-2 4">6 <!ENTITY releasedate "February 2 4th, 2004">5 <!ENTITY version "CVS-2004-02-25"> 6 <!ENTITY releasedate "February 25th, 2004"> 7 7 <!ENTITY milestone "5.2"> 8 8 <!ENTITY nbsp " ">
Note:
See TracChangeset
for help on using the changeset viewer.