From 8a8177f9b93774426694ffd5b72e4f8aef4f316d Mon Sep 17 00:00:00 2001 From: Bruce Dubbs Date: Sun, 3 Aug 2014 16:37:17 +0000 Subject: [PATCH] Intermediate commit to test a change to gcc. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@10672 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter05/gcc-pass1.xml | 4 ++++ chapter05/gcc-pass2.xml | 4 ++++ chapter06/gcc.xml | 15 ++++++++++----- chapter06/pkgmgt.xml | 12 ++++-------- 4 files changed, 22 insertions(+), 13 deletions(-) diff --git a/chapter05/gcc-pass1.xml b/chapter05/gcc-pass1.xml index b0fd383f8..49612eba7 100644 --- a/chapter05/gcc-pass1.xml +++ b/chapter05/gcc-pass1.xml @@ -105,6 +105,10 @@ done sed -i '/k prot/agcc_cv_libc_provides_ssp=yes' gcc/configure + Also fix a problem identified upstream: + +sed -i 's/if \((code.*))\)/if (\1 \&\& \!DEBUG_INSN_P (insn))/' gcc/sched-deps.c + The GCC documentation recommends building GCC outside of the source directory in a dedicated build directory: diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml index 1dce58834..1bd4c4a20 100644 --- a/chapter05/gcc-pass2.xml +++ b/chapter05/gcc-pass2.xml @@ -95,6 +95,10 @@ mv -v gmp-&gmp-extracted-version; gmp tar -xf ../mpc-&mpc-version;.tar.gz mv -v mpc-&mpc-version; mpc + As in the first build of GCC, fix a problem identified upstream: + +sed -i 's/if \((code.*))\)/if (\1 \&\& \!DEBUG_INSN_P (insn))/' gcc/sched-deps.c + Create a separate build directory again: mkdir -v ../gcc-build diff --git a/chapter06/gcc.xml b/chapter06/gcc.xml index e7efba79a..8dc997b01 100644 --- a/chapter06/gcc.xml +++ b/chapter06/gcc.xml @@ -40,6 +40,11 @@ Installation of GCC + + As in Chapter 5, fix a problem identified upstream: + +sed -i 's/if \((code.*))\)/if (\1 \&\& \!DEBUG_INSN_P (insn))/' gcc/sched-deps.c + Unless the test results are vastly different from those at the above URL, it is safe to continue. @@ -321,7 +326,7 @@ mv -v /usr/lib/*gdb.py /usr/share/gdb/auto-load/usr/lib libasan.{a,so}, libatomic.{a,so}, libgcc.a, libgcc_eh.a, libgcc_s.so, libgcov.a, libgomp.{a,so}, libiberty.a, libitm.{a,so}, - liblto_plugin.so, libmudflap.{a,so}, libmudflapth.{a,so}, + liblto_plugin.so, libquadmath.{a,so}, libssp.{a,so}, libssp_nonshared.a, libstdc++.{a,so}, libsupc++.a and libtsan.{a,so} @@ -501,7 +506,7 @@ mv -v /usr/lib/*gdb.py /usr/share/gdb/auto-load/usr/lib - + libquadmath diff --git a/chapter06/pkgmgt.xml b/chapter06/pkgmgt.xml index 67ffd1cd7..b4734aba0 100644 --- a/chapter06/pkgmgt.xml +++ b/chapter06/pkgmgt.xml @@ -51,14 +51,10 @@ - If one of the toolchain packages (Glibc, GCC or Binutils) needs - to be upgraded to a newer minor version, it is safer to rebuild LFS. - Though you may be able to get by rebuilding all - the packages in their dependency order, we do not recommend it. For - example, if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer - to rebuild. For micro version updates, a simple reinstallation usually - works, but is not guaranteed. For example, upgrading from glibc-2.3.4 - to glibc-2.3.5 will not usually cause any problems. + If Glibc needs to be upgraded to a newer version, (e.g. from + glibc-2.19 to glibc-2.20, it is safer to rebuild LFS. Though you + may be able to rebuild all the packages in their + dependency order, we do not recommend it.