| 1 | <sect2>
|
|---|
| 2 | <title>Installation of Glibc</title>
|
|---|
| 3 |
|
|---|
| 4 | <para>This package requires its patch to be applied before you can
|
|---|
| 5 | install it. Make sure it's unpacked before running the installation
|
|---|
| 6 | commands.</para>
|
|---|
| 7 |
|
|---|
| 8 | <para>Before starting to install glibc, you must cd into the
|
|---|
| 9 | glibc-&glibc-version; directory and unpack glibc-linuxthreads inside
|
|---|
| 10 | the glibc-&glibc-version; directory, not in /usr/src as you normally
|
|---|
| 11 | would do.</para>
|
|---|
| 12 |
|
|---|
| 13 | <para>This package is known to behave badly when you have changed its
|
|---|
| 14 | default optimization flags (including the -march and -mcpu options). Glibc
|
|---|
| 15 | is best left alone. Therefore, if you have defined any environment variables
|
|---|
| 16 | that override default optimizations, such as CFLAGS and CXXFLAGS, we
|
|---|
| 17 | recommend unsetting or modifying them when building Glibc. You have
|
|---|
| 18 | been warned.</para>
|
|---|
| 19 |
|
|---|
| 20 | <para>Also, don't pass the --enable-kernel option to the configure
|
|---|
| 21 | script. It's known to cause segmentation faults when other packages like
|
|---|
| 22 | fileutils, make and tar are linked against it.</para>
|
|---|
| 23 |
|
|---|
| 24 | <para>Basically, compiling Glibc in any other way than the book suggests
|
|---|
| 25 | is putting your system at very high risk.</para>
|
|---|
| 26 |
|
|---|
| 27 | <para>Install Glibc by running the following commands:</para>
|
|---|
| 28 |
|
|---|
| 29 | <para><screen><userinput>patch -Np1 -i ../glibc-&glibc-patch-version;.patch &&
|
|---|
| 30 | touch /etc/ld.so.conf &&
|
|---|
| 31 | mkdir ../glibc-build &&
|
|---|
| 32 | cd ../glibc-build &&
|
|---|
| 33 | ../glibc-&glibc-version;/configure --prefix=/usr \
|
|---|
| 34 | --enable-add-ons --libexecdir=/usr/bin &&
|
|---|
| 35 | echo "cross-compiling = no" > configparms &&
|
|---|
| 36 | make &&
|
|---|
| 37 | make install &&
|
|---|
| 38 | make localedata/install-locales &&
|
|---|
| 39 | exec /static/bin/bash --login</userinput></screen></para>
|
|---|
| 40 |
|
|---|
| 41 | <para>An alternative to running <userinput>make
|
|---|
| 42 | localedata/install-locales</userinput> is to only install those locales
|
|---|
| 43 | which you need or want. This can be achieved using the localedef
|
|---|
| 44 | command. Information on this can be found in the INSTALL
|
|---|
| 45 | file in the glibc-&glibc-version; tree. One thing to note is that the
|
|---|
| 46 | <userinput>localedef</userinput> program assumes that the <filename
|
|---|
| 47 | class="directory">/usr/lib/locale</filename> directory exists, so you need
|
|---|
| 48 | to create it first.</para>
|
|---|
| 49 |
|
|---|
| 50 | <para>During the configure stage you will see the following warning:</para>
|
|---|
| 51 |
|
|---|
| 52 | <blockquote><screen>configure: warning:
|
|---|
| 53 | *** These auxiliary programs are missing or too old: msgfmt
|
|---|
| 54 | *** some features will be disabled.
|
|---|
| 55 | *** Check the INSTALL file for required versions.</screen></blockquote>
|
|---|
| 56 |
|
|---|
| 57 | <para>The missing msgfmt (from the gettext package which we will install
|
|---|
| 58 | later in this chapter) won't cause any problems. msgfmt is used to generate
|
|---|
| 59 | the binary translation files that are used to make your system talk in a
|
|---|
| 60 | different language. Because these translation files have already been
|
|---|
| 61 | generated for you, there is no need for msgfmt. You'd only need msgfmt if
|
|---|
| 62 | you change the translation source files (the <filename>*.po</filename>
|
|---|
| 63 | files in the <filename class="directory">po</filename> subdirectory) which
|
|---|
| 64 | would require you to re-generate the binary files.</para>
|
|---|
| 65 |
|
|---|
| 66 | </sect2>
|
|---|
| 67 |
|
|---|
