Changeset 8a8177f9
- Timestamp:
- 08/03/2014 04:37:17 PM (10 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, 7.6, 7.7, 7.8, 7.9, 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:
- c26c46ba
- Parents:
- 0bf4dfe
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/gcc-pass1.xml
r0bf4dfe r8a8177f9 105 105 106 106 <screen><userinput remap="pre">sed -i '/k prot/agcc_cv_libc_provides_ssp=yes' gcc/configure</userinput></screen> 107 108 <para>Also fix a problem identified upstream:</para> 109 110 <screen><userinput remap="pre">sed -i 's/if \((code.*))\)/if (\1 \&\& \!DEBUG_INSN_P (insn))/' gcc/sched-deps.c</userinput></screen> 107 111 108 112 <para>The GCC documentation recommends building GCC outside of the -
chapter05/gcc-pass2.xml
r0bf4dfe r8a8177f9 95 95 tar -xf ../mpc-&mpc-version;.tar.gz 96 96 mv -v mpc-&mpc-version; mpc</userinput></screen> 97 98 <para>As in the first build of GCC, fix a problem identified upstream:</para> 99 100 <screen><userinput remap="pre">sed -i 's/if \((code.*))\)/if (\1 \&\& \!DEBUG_INSN_P (insn))/' gcc/sched-deps.c</userinput></screen> 97 101 98 102 <para>Create a separate build directory again:</para> -
chapter06/gcc.xml
r0bf4dfe r8a8177f9 41 41 <sect2 role="installation"> 42 42 <title>Installation of GCC</title> 43 44 <para>As in Chapter 5, fix a problem identified upstream:</para> 45 46 <screen><userinput remap="pre">sed -i 's/if \((code.*))\)/if (\1 \&\& \!DEBUG_INSN_P (insn))/' gcc/sched-deps.c</userinput></screen> 47 43 48 <!-- 44 49 <para>First fix a problem identified upstream that causes some … … 131 136 132 137 <para>A few unexpected failures cannot always be avoided. The GCC developers 133 are usually aware of these issues, but have not resolved them yet. In138 are usually aware of these issues, but have not resolved them yet. <!-- In 134 139 particular, the <filename class="libraryfile">libmudflap</filename> tests 135 140 are known to be particularly problematic as a result of a bug in GCC 136 (<ulink url="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20003"/>). 141 (<ulink url="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20003"/>). --> 137 142 Unless the test results are vastly different from those at the above URL, 138 143 it is safe to continue.</para> … … 322 327 <seg>libasan.{a,so}, libatomic.{a,so}, libgcc.a, libgcc_eh.a, 323 328 libgcc_s.so, libgcov.a, libgomp.{a,so}, libiberty.a, libitm.{a,so}, 324 liblto_plugin.so, libmudflap.{a,so}, libmudflapth.{a,so},329 liblto_plugin.so, 325 330 libquadmath.{a,so}, libssp.{a,so}, 326 331 libssp_nonshared.a, libstdc++.{a,so}, libsupc++.a and libtsan.{a,so}</seg> … … 502 507 </listitem> 503 508 </varlistentry> 504 509 <!-- 505 510 <varlistentry id="libmudflap"> 506 511 <term><filename class="libraryfile">libmudflap</filename></term> … … 513 518 </listitem> 514 519 </varlistentry> 515 520 --> 516 521 <varlistentry id="libquadmath"> 517 522 <term><filename class="libraryfile">libquadmath</filename></term> -
chapter06/pkgmgt.xml
r0bf4dfe r8a8177f9 52 52 <itemizedlist> 53 53 <listitem> 54 <para>If one of the toolchain packages (Glibc, GCC or Binutils) needs 55 to be upgraded to a newer minor version, it is safer to rebuild LFS. 56 Though you <emphasis>may</emphasis> be able to get by rebuilding all 57 the packages in their dependency order, we do not recommend it. For 58 example, if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer 59 to rebuild. For micro version updates, a simple reinstallation usually 60 works, but is not guaranteed. For example, upgrading from glibc-2.3.4 61 to glibc-2.3.5 will not usually cause any problems.</para> 54 <para>If Glibc needs to be upgraded to a newer version, (e.g. from 55 glibc-2.19 to glibc-2.20, it is safer to rebuild LFS. Though you 56 <emphasis>may</emphasis> be able to rebuild all the packages in their 57 dependency order, we do not recommend it. </para> 62 58 </listitem> 63 59
Note:
See TracChangeset
for help on using the changeset viewer.