Changeset e9cab664 for general/prog/gcc.xml

Timestamp:

06/24/2017 11:13:15 AM (7 years ago)

Author:

Pierre Labastie <pieere@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

9401155

Parents:

7dcab6e

Message:

Apache-2.4.26 and explanation for
GCC include-fixed headers

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@18863 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• general/prog/gcc.xml (modified) (1 diff)

general/prog/gcc.xml

@@ -59 +59 @@
 
       <para>
-        The 5.1.0 version of GCC introduces an incompatible ABI change in the
-        C++ library <filename>libstdc++.so</filename>. This does not prevent
-        using programs compiled with the previous version of <application>GCC
-        </application>, since both old and new symbols are available in the
-        library. But compiling, with the new version, programs which use
-        libraries compiled with the old version is likely to give errors. So,
-        if you are upgrading from any previous version prior to 5.1.0, you have
-        two solutions:
-        recompile all the libraries with the new version, or use the <option>
-        --with-default-libstdcxx-abi</option> switch to configure.
+        Some system headers need to be fixed to be used with GCC. This is done
+        during the installation of GCC, and the <quote>fixed</quote> headers
+        are installed in <filename class="directory">
+        /usr/lib/gcc/&lt;machine triplet&gt;/&lt;GCC version&gt;/include-fixed
+        </filename>. This is harmless if GCC is built during the LFS stage. But
+        if you reinstall GCC in BLFS, some of the BLFS packages may be
+        <quote>fixed</quote>. If one of those packages is reinstalled
+        afterwards, the <quote>fixed</quote> headers are not updated, which may
+        lead to version mismatches. In case that happens, the
+        <quote>fixed</quote> headers must be updated by running (as
+        <systemitem class="username">root</systemitem>):
+        <command>
+         /usr/libexec/gcc/x86_64-pc-linux-gnu/7.1.0/install-tools/mkheaders
+        </command>. The machine triplet may be different on a 32bit system.
       </para>
     </caution>