We recommend installing the following GNU tools before attempting to build the GNU C Library:
make3.79 or newer
You need the latest version of GNU
make. Modifying the GNU C Library
to work with other
make programs would be so difficult that
we recommend you port GNU
make instead. Really. We
make version 3.79. All earlier versions have severe
bugs or lack features.
GCC 4.6 or higher is required. In general it is recommended to use the newest version of the compiler that is known to work for building the GNU C Library, as newer compilers usually produce better code. As of release time, GCC 4.9.2 is the newest compiler verified to work to build the GNU C Library.
You can use whatever compiler you like to compile programs that use the GNU C Library.
Check the FAQ for any special compiler issues on particular platforms.
binutils2.22 or later
You must use GNU
binutils (as and ld) to build the GNU C Library.
No other assembler or linker has the necessary functionality at the
moment. As of release time, GNU
binutils 2.25 is the newest
verified to work to build the GNU C Library.
texinfo4.7 or later
To correctly translate and install the Texinfo documentation you need
this version of the
texinfo package. Earlier versions do not
understand all the tags used in the document, and the installation
mechanism for the info files is not present or works differently.
As of release time,
texinfo 5.2 is the newest verified to work
to build the GNU C Library.
awk3.1.2, or higher
awk is used in several places to generate files.
gawk extensions are used, including the
function, which was introduced in version 3.1.2 of
Perl is not required, but it is used if present to test the installation. We may decide to use it elsewhere in the future.
sed3.02 or newer
Sed is used in several places to generate files. Most scripts work
with any version of
sed. The known exception is the script
po2test.sed in the
intl subdirectory which is used to
msgs.h for the test suite. This script works correctly
only with GNU
sed 3.02. If you like to run the test suite, you
should definitely upgrade
If you change any of the configure.ac files you will also need
and if you change any of the message translation files you will need
gettext0.10.36 or later
If you wish to regenerate the
yacc parser code in the intl
subdirectory you will need
bison2.7 or later
You may also need these packages if you upgrade your source tree using patches, although we try to avoid this.