Changeset 1f53626
- Timestamp:
- 09/16/2003 07:28:26 AM (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, 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:
- 2260572
- Parents:
- 18b65e2b
- Files:
-
- 12 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
r18b65e2b r1f53626 88 88 </para></listitem> 89 89 90 <listitem><para>September 16th, 2003 [greg]: Chapters 5 and 6 - Locking in 91 Glibc and Re-adjusting the toolchain: Added sanity checks.</para></listitem> 92 93 <listitem><para>September 16th, 2003 [greg]: Chapters 5 and 6 - Binutils, GCC, 94 and Glibc: Added notes on the test suites.</para></listitem> 95 90 96 <listitem><para>September 14th, 2003 [greg]: Chapter 6 - Revised chroot 91 97 command: Removed no longer needed set +h.</para></listitem> -
chapter05/binutils-pass1-inst.xml
r18b65e2b r1f53626 7 7 because both Glibc and GCC perform various tests on the available linker and 8 8 assembler to determine which of their own features to enable.</para> 9 10 <note><para>Even though Binutils is an important toolchain package, we are not 11 going to run the testsuite at this early stage. Firstly, the testsuite 12 framework is not yet in place and secondly, the programs from this first pass 13 will soon be overwritten by those installed in the second pass.</para></note> 9 14 10 15 <para>This package is known to behave badly when you have changed its default -
chapter05/binutils-pass2-inst.xml
r18b65e2b r1f53626 3 3 <sect2> 4 4 <title>Re-installation of Binutils</title> 5 6 <note><para>It's worth noting that the Binutils testsuite we run in this 7 chapter is considered not as critical as the one we run in Chapter 6.</para> 8 </note> 5 9 6 10 <para>First create a separate build directory again:</para> -
chapter05/gcc-pass1-inst.xml
r18b65e2b r1f53626 6 6 <para>Unpack only the GCC-core tarball, as we won't be needing a C++ compiler 7 7 for the moment.</para> 8 9 <note><para>Even though GCC is an important toolchain package, we are not 10 going to run the testsuite at this early stage. Firstly, the testsuite 11 framework is not yet in place and secondly, the programs from this first pass 12 will soon be overwritten by those installed in the second pass.</para></note> 8 13 9 14 <para>This package is known to behave badly when you have changed its -
chapter05/gcc-pass2-inst.xml
r18b65e2b r1f53626 11 11 which does not properly support the devpts filesystem will cause most of 12 12 these tests to fail.</para> 13 14 <note><para>It's worth noting that the GCC testsuite we run in this chapter is 15 considered not as critical as the one we run in Chapter 6.</para></note> 13 16 14 17 <para>Unpack all three GCC tarballs in one and the same working directory. -
chapter05/glibc-inst.xml
r18b65e2b r1f53626 8 8 Glibc-linuxthreads in that directory, not in <filename>/usr/src</filename> as 9 9 you would normally do.</para> 10 11 <note><para>We are going to run the testsuite for Glibc in this chapter. 12 However, it's worth noting that the Glibc testsuite we run in this chapter is 13 considered not as critical as the one we run in Chapter 6.</para></note> 10 14 11 15 <para>This package is known to behave badly when you have changed its -
chapter05/lockingglibc.xml
r18b65e2b r1f53626 46 46 <para><screen><userinput>rm -f /tools/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen></para> 47 47 48 <caution><para>It is imperative at this point to stop and ensure that the 49 basic functionality of the new toolchain is working as expected. We are going 50 to perform a simple sanity check:</para> 51 52 <para><screen><userinput>echo 'main(){}' > dummy.c 53 gcc dummy.c 54 readelf -l a.out | grep ': /tools'</userinput></screen></para> 55 56 <para>If everything is working correctly, the output of the last command will 57 be:</para> 58 59 <para><screen>[Requesting program interpreter: /tools/lib/ld-linux.so.2] 60 </screen></para> 61 62 <para>If you did not receive the output as shown above then something is 63 seriously wrong. You will need to investigate and retrace your steps to find 64 out where the problem is and correct it. There is no point in continuing 65 until this is done. Most likely, something went wrong with the specs file 66 amendment above. Note especially that <filename>/tools/lib</filename> appears 67 as the prefix of our dynamic linker. Of course, if you are working on a 68 platform where the name of the dynamic linker is something other than 69 <filename>ld-linux.so.2</filename> then the output will be slightly different. 70 </para> 71 72 <para>Once you are satisfied that all is well, clean up the test files:</para> 73 74 <para><screen><userinput>rm dummy.c a.out</userinput></screen></para> 75 </caution> 76 48 77 <para>This completes the installation of the self-contained toolchain, which 49 78 can now be used to build the rest of the temporary tools.</para> -
chapter06/adjustingtoolchain.xml
r18b65e2b r1f53626 44 44 located in <filename class="directory">/tools/lib</filename>.</para> 45 45 46 <caution><para>It is imperative at this point to stop and ensure that the 47 basic functionality of the adjusted toolchain is working as expected. We are 48 going to perform a simple sanity check:</para> 49 50 <para><screen><userinput>echo 'main(){}' > dummy.c 51 gcc dummy.c 52 readelf -l a.out | grep ': /lib'</userinput></screen></para> 53 54 <para>If everything is working correctly, the output of the last command will 55 be:</para> 56 57 <para><screen>[Requesting program interpreter: /lib/ld-linux.so.2] 58 </screen></para> 59 60 <para>If you did not receive the output as shown above then something is 61 seriously wrong. You will need to investigate and retrace your steps to find 62 out where the problem is and correct it. There is no point in continuing 63 until this is done. Most likely, something went wrong with the specs file 64 amendment above. Note especially that <filename>/lib</filename> now appears as 65 the prefix of our dynamic linker. Of course, if you are working on a platform 66 where the name of the dynamic linker is something other than <filename> 67 ld-linux.so.2</filename> then the output will be slightly different.</para> 68 69 <para>Once you are satisfied that all is well, clean up the test files:</para> 70 71 <para><screen><userinput>rm dummy.c a.out</userinput></screen></para> 72 </caution> 73 46 74 </sect1> 47 75 -
chapter06/binutils-inst.xml
r18b65e2b r1f53626 2 2 3 3 <sect2><title>Installation of Binutils</title> 4 5 <note><para>The testsuite for Binutils in this chapter is considered 6 <emphasis>critical</emphasis>. Do not skip it under any circumstances.</para> 7 </note> 4 8 5 9 <para>This package is known to behave badly when you have changed its -
chapter06/gcc-inst.xml
r18b65e2b r1f53626 3 3 <sect2> 4 4 <title>Installation of GCC</title> 5 6 <note><para>The testsuite for GCC in this chapter is considered <emphasis> 7 critical</emphasis>. Do not skip it under any circumstances.</para></note> 5 8 6 9 <para>This package is known to behave badly when you have changed its -
chapter06/glibc-inst.xml
r18b65e2b r1f53626 9 9 ldscripts before the Glibc install, because the Glibc autoconf tests would then 10 10 give bogus results and thus defeat our goal of achieving a clean build.</para> 11 12 <note><para>The testsuite for Glibc in this chapter is considered <emphasis> 13 critical</emphasis>. Do not skip it under any circumstances.</para></note> 11 14 12 15 <para>Before starting to build Glibc, remember to unpack the Glibc-linuxthreads -
index.xml
r18b65e2b r1f53626 4 4 5 5 6 <!ENTITY version "2003091 5">7 <!ENTITY releasedate "September 1 5th, 2003">6 <!ENTITY version "20030916"> 7 <!ENTITY releasedate "September 16th, 2003"> 8 8 <!ENTITY nbsp " "> 9 9
Note:
See TracChangeset
for help on using the changeset viewer.