Changeset d0a6c4c for chapter05


Ignore:
Timestamp:
01/20/2004 05:59:05 AM (20 years ago)
Author:
Greg Schafer <greg@…>
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.0, 6.1, 6.1.1, 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, v5_1, v5_1_1, 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:
e5888f5
Parents:
fae442d5
Message:

Upgraded to Glibc-2.3.3, Kbd-1.12, Perl-5.8.3 and Shadow-4.0.4.1.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3177 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Location:
chapter05
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • chapter05/coreutils.xml

    rfae442d5 rd0a6c4c  
    1616<title>Installation of Coreutils</title>
    1717
    18 <para>Prepare Coreutils for compilation:</para>
     18<para>Coreutils has an issue when compiled against Glibc-&glibc-version;.
     19Without the patch below, some of the Coreutils utilities (head, tail, sort etc)
     20will reject their traditional syntax which has been in use for approximately 30
     21years. The old syntax is so pervasive that compatibility must be preserved until
     22the many places where it is used can be updated. More details are provided in
     23the comments inside the patch itself. Use of this patch is by no means
     24compulsory but opting not to use it means you'll have deal with the consequences
     25yourself, i.e. patch the many software packages that use the old syntax. Apply
     26the patch:</para>
     27
     28<screen><userinput>patch -Np1 -i ../&coreutils-posixver-patch;</userinput></screen>
     29
     30<para>Now prepare Coreutils for compilation:</para>
    1931
    2032<screen><userinput>./configure --prefix=/tools</userinput></screen>

  • chapter05/glibc.xml

    rfae442d5 rd0a6c4c  
    1414<title>Installation of Glibc</title>
    1515
    16 <para>Before starting to install Glibc, you must <userinput>cd</userinput>
    17 into the <filename>glibc-&glibc-version;</filename> directory and unpack
    18 Glibc-linuxthreads in that directory, not in the directory where you usually
    19 unpack all the sources.</para>
    20 
    2116<para>This package is known to behave badly when you have changed its
    2217default optimization flags (including the -march and -mcpu options).
    … …  
    2823is putting the stability of your system at risk.</para>
    2924
    30 <para>Glibc has a subtle problem when compiled with GCC &gcc-version;.
    31 Apply the following patch to fix this:</para>
    32 
    33 <screen><userinput>patch -Np1 -i ../&glibc-sscanf-patch;</userinput></screen>
    34 
    3525<para>The Glibc documentation recommends building Glibc outside of the source
    3626directory in a dedicated build directory:</para>
    … …  
    4131<para>Next, prepare Glibc for compilation:</para>
    4232
    43 <screen><userinput>../glibc-&glibc-version;/configure --prefix=/tools \
    44 &nbsp;&nbsp;&nbsp;&nbsp;--disable-profile --enable-add-ons \
     33<screen><userinput>../&glibc-dir;/configure --prefix=/tools \
     34&nbsp;&nbsp;&nbsp;&nbsp;--disable-profile --enable-add-ons=linuxthreads \
    4535&nbsp;&nbsp;&nbsp;&nbsp;--with-headers=/tools/include \
    4636&nbsp;&nbsp;&nbsp;&nbsp;--with-binutils=/tools/bin \
    47 &nbsp;&nbsp;&nbsp;&nbsp;--without-gd</userinput></screen>
     37&nbsp;&nbsp;&nbsp;&nbsp;--without-gd --without-cvs</userinput></screen>
    4838
    4939<para>The meaning of the configure options:</para>
    … …  
    5444plan to do profiling.</para></listitem>
    5545
    56 <listitem><para><userinput>--enable-add-ons</userinput>: This enables any
    57 add-ons that were installed with Glibc, in our case Linuxthreads.</para></listitem>
     46<listitem><para><userinput>--enable-add-ons=linuxthreads</userinput>: This
     47tells Glibc to use the Linuxthreads add-on as its threading
     48library.</para></listitem>
    5849
    5950<listitem><para><userinput>--with-binutils=/tools/bin</userinput> and
    … …  
    6354Glibc build.</para></listitem>
    6455
    65 <listitem><para><userinput> --without-gd</userinput>: This switch ensures
     56<listitem><para><userinput>--without-gd</userinput>: This switch ensures
    6657that we don't build the <userinput>memusagestat</userinput> program, which
    6758strangely enough insists on linking against the host's libraries (libgd,
    6859libpng, libz, and so forth).</para></listitem>
     60
     61<listitem><para><userinput>--without-cvs</userinput>: This is meant to prevent
     62the Makefiles from attempting automatic CVS commits when using a CVS snapshot.
     63But it's not actually needed these days. We use it because it silences an
     64annoying but harmless warning about a missing <filename>autoconf</filename>
     65program.</para></listitem>
    6966</itemizedlist>
    7067
    … …  
    159156<screen><userinput>make localedata/install-locales</userinput></screen>
    160157
    161 <para>An alternative to running the previous command is to install only
    162 those locales which you need or want. This can be achieved by using the
    163 <userinput>localedef</userinput> command. Information on this can be
    164 found in the <filename>INSTALL</filename> file in the
    165 <filename>glibc-&glibc-version;</filename> source. However, there are a number
    166 of locales that are essential for the tests of future packages to pass, in
    167 particular, the <emphasis>libstdc++</emphasis> tests from GCC.  The following
    168 instructions, instead of the install-locales target above, will install
    169 the minimum set of locales necessary for the tests to run successfully:</para>
     158<para>An alternative to running the previous command is to install only those
     159locales which you need or want. This can be achieved by using the
     160<userinput>localedef</userinput> command. Information on this can be found in
     161the <filename>INSTALL</filename> file in the Glibc source. However, there are
     162a number of locales that are essential for the tests of future packages to
     163pass, in particular, the <emphasis>libstdc++</emphasis> tests from GCC. The
     164following instructions, instead of the install-locales target above, will
     165install the minimum set of locales necessary for the tests to run
     166successfully:</para>
    170167
    171168<screen><userinput>mkdir -p /tools/lib/locale
Note: See TracChangeset for help on using the changeset viewer.