Changeset dc0e915
- Timestamp:
- 06/14/2005 04:15:58 PM (19 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.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, 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:
- 32ae9c7
- Parents:
- a4ee3d2
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
ra4ee3d2 rdc0e915 89 89 </listitem> 90 90 91 <listitem><para>June 14th, 2005 [archaic]: Removed references to separate gcc 92 tarballs (gcc-core, gcc-g++, etc.)</para></listitem> 93 91 94 <listitem><para>June 14th, 2005 [archaic]: Updated all build sizes.</para></listitem> 92 95 -
chapter05/gcc-pass1.xml
ra4ee3d2 rdc0e915 29 29 <sect2 role="installation"> 30 30 <title>Installation of GCC</title> 31 32 <para>Unpack only the gcc-core tarball because neither the C++33 compiler nor the test suite will be needed here.</para>34 31 35 32 <para>This package is known to have issues when its default … … 77 74 <term><parameter>--enable-languages=c</parameter></term> 78 75 <listitem><para>This option ensures that only the C compiler is built. 79 This option is only needed when you have downloaded and unpacked the 80 full GCC tarball, as opposed to just the gcc-core 81 tarball.</para></listitem> 76 </para></listitem> 82 77 </varlistentry> 83 78 </variablelist> -
chapter05/gcc-pass2.xml
ra4ee3d2 rdc0e915 58 58 consult the LFS Wiki at <ulink url="&wiki-root;"/> for more 59 59 information on how to get PTYs working.</para> 60 61 <para>Because the C and the C++ compilers will be built, unpack both62 the core and the g++ tarballs (as well as test suite, if you want to63 run the tests). By unpacking them in the working directory, they will64 all unfold into a single <filename65 class="directory">gcc-&gcc-version;/</filename> subdirectory.</para>66 60 67 61 <para>First correct a known problem and make an essential adjustment:</para> -
chapter06/gcc.xml
ra4ee3d2 rdc0e915 39 39 unset them when building GCC.</para> 40 40 41 <para>Unpack both the gcc-core and the gcc-g++ tarballs—they will unpack42 into the same directory. Likewise, extract the gcc-testsuite tarball.</para>43 44 41 <para>Apply only the No-Fixincludes patch (not the Specs patch) also 45 42 used in the previous chapter:</para>
Note:
See TracChangeset
for help on using the changeset viewer.