Context Navigation

-              rf3125bf
+              r51a1403
     </listitem>
     <listitem os="c3">
       <para>Glibc and GCC files (<filename class="directory">/lib</filename>
+      <para>EGlibc and GCC files (<filename class="directory">/lib</filename>
       and <filename class="directory">/usr/lib</filename>) with debugging
       symbols: 87 MB</para>
     </listitem>
     <listitem os="c4">
       <para>Glibc and GCC files without debugging symbols: 16 MB</para>
+      <para>EGlibc and GCC files without debugging symbols: 16 MB</para>
     </listitem>
   </itemizedlist>

BOOK/final-system/common/bash.xml

rf3125bf	r51a1403
36	36	become an unprivileged user, this combination will cause Bash to build
37	37	without <emphasis>process substitution</emphasis>, which will break one
38		of the c++ test scripts in <literal>glibc</literal>. The following prevents
	38	of the c++ test scripts in <literal>eglibc</literal>. The following prevents
39	39	future problems by skipping tests that can not run while cross-compiling
40	40	or that do not run properly:</para>

rf3125bf	r51a1403
29	29
30	30	<para os="s1">The following command renames the internal implementation of
31		futimens to gl_futimens as newer versions of Glibc provide an incompatible
	31	futimens to gl_futimens as newer versions of EGlibc provide an incompatible
32	32	version:</para>
33	33

rf3125bf	r51a1403
32	32	the code and build tools. Also note that the <option>-march</option>
33	33	and <option>-mtune</option> options may cause problems with the toolchain
34		packages (Binutils, GCC and Glibc). The small potential gains achieved in
	34	packages (Binutils, GCC and EGlibc). The small potential gains achieved in
35	35	using compiler optimizations are often outweighed by the risks. First-time
36	36	builders of CLFS are encouraged to build without custom optimizations.

-              rf3125bf
+              r51a1403
     <itemizedlist>
       <listitem>
         <para>If one of the toolchain packages (Glibc, GCC or Binutils) needs
+        <para>If one of the toolchain packages (EGlibc, GCC or Binutils) needs
         to be upgraded to a newer minor version, it is safer to
         rebuild CLFS. Though you <emphasis>may</emphasis> 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
+        recommend it. For example, if eglibc-2.2.x needs to be updated to
+        eglibc-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
+        example, upgrading from eglibc-2.3.4 to glibc-2.3.5 will not
         usually cause any problems.</para>
       </listitem>

Note: See TracChangeset for help on using the changeset viewer.