2006-03-01 10:05:04 +00:00
|
|
|
Installing the GNU C Library
|
|
|
|
|
****************************
|
1998-05-18 09:53:46 +00:00
|
|
|
|
2012-05-16 18:50:39 +00:00
|
|
|
Before you do anything else, you should read the FAQ at
|
|
|
|
|
`http://sourceware.org/glibc/wiki/FAQ'. It answers common questions
|
1998-05-18 09:53:46 +00:00
|
|
|
and describes problems you may experience with compilation and
|
2012-05-16 18:50:39 +00:00
|
|
|
installation.
|
1998-05-18 09:53:46 +00:00
|
|
|
|
2013-12-19 01:53:22 +00:00
|
|
|
Features can be added to the GNU C Library via "add-on" bundles. These
|
|
|
|
|
are separate tar files, which you unpack into the top level of the
|
|
|
|
|
source tree. Then you give `configure' the `--enable-add-ons' option
|
|
|
|
|
to activate them, and they will be compiled into the library.
|
1998-11-04 23:04:21 +00:00
|
|
|
|
|
|
|
|
You will need recent versions of several GNU tools: definitely GCC
|
1998-11-05 13:03:24 +00:00
|
|
|
and GNU Make, and possibly others. *Note Tools for Compilation::,
|
1998-11-04 23:04:21 +00:00
|
|
|
below.
|
|
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
Configuring and compiling the GNU C Library
|
|
|
|
|
===========================================
|
1998-11-04 23:04:21 +00:00
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
The GNU C Library cannot be compiled in the source directory. You must
|
|
|
|
|
build it in a separate build directory. For example, if you have
|
|
|
|
|
unpacked the GNU C Library sources in `/src/gnu/glibc-VERSION', create
|
|
|
|
|
a directory `/src/gnu/glibc-build' to put the object files in. This
|
|
|
|
|
allows removing the whole build directory in case an error occurs,
|
|
|
|
|
which is the safest way to get a fresh start and should always be done.
|
1998-11-04 23:04:21 +00:00
|
|
|
|
2002-04-06 01:45:15 +00:00
|
|
|
From your object directory, run the shell script `configure' located
|
1998-11-04 23:04:21 +00:00
|
|
|
at the top level of the source tree. In the scenario above, you'd type
|
|
|
|
|
|
2012-02-21 01:01:28 +00:00
|
|
|
$ ../glibc-VERSION/configure ARGS...
|
1998-11-04 23:04:21 +00:00
|
|
|
|
2006-03-06 10:59:43 +00:00
|
|
|
Please note that even though you're building in a separate build
|
2012-05-18 18:30:51 +00:00
|
|
|
directory, the compilation may need to create or modify files and
|
|
|
|
|
directories in the source directory.
|
1999-07-27 02:07:01 +00:00
|
|
|
|
2006-03-06 10:59:43 +00:00
|
|
|
`configure' takes many options, but the only one that is usually
|
|
|
|
|
mandatory is `--prefix'. This option tells `configure' where you want
|
2012-02-28 14:44:20 +00:00
|
|
|
the GNU C Library installed. This defaults to `/usr/local', but the
|
|
|
|
|
normal setting to install as the standard system library is
|
|
|
|
|
`--prefix=/usr' for GNU/Linux systems and `--prefix=' (an empty prefix)
|
|
|
|
|
for GNU/Hurd systems.
|
1998-11-04 23:04:21 +00:00
|
|
|
|
|
|
|
|
It may also be useful to set the CC and CFLAGS variables in the
|
|
|
|
|
environment when running `configure'. CC selects the C compiler that
|
|
|
|
|
will be used, and CFLAGS sets optimization options for the compiler.
|
|
|
|
|
|
1999-09-05 23:34:47 +00:00
|
|
|
The following list describes all of the available options for
|
|
|
|
|
`configure':
|
1998-11-04 23:04:21 +00:00
|
|
|
|
|
|
|
|
`--prefix=DIRECTORY'
|
|
|
|
|
Install machine-independent data files in subdirectories of
|
|
|
|
|
`DIRECTORY'. The default is to install in `/usr/local'.
|
|
|
|
|
|
|
|
|
|
`--exec-prefix=DIRECTORY'
|
|
|
|
|
Install the library and other machine-dependent files in
|
|
|
|
|
subdirectories of `DIRECTORY'. The default is to the `--prefix'
|
1999-09-05 23:34:47 +00:00
|
|
|
directory if that option is specified, or `/usr/local' otherwise.
|
1998-11-04 23:04:21 +00:00
|
|
|
|
|
|
|
|
`--with-headers=DIRECTORY'
|
|
|
|
|
Look for kernel header files in DIRECTORY, not `/usr/include'.
|
2012-02-28 14:44:20 +00:00
|
|
|
The GNU C Library needs information from the kernel's header files
|
|
|
|
|
describing the interface to the kernel. The GNU C Library will
|
|
|
|
|
normally look in `/usr/include' for them, but if you specify this
|
|
|
|
|
option, it will look in DIRECTORY instead.
|
1998-11-04 23:04:21 +00:00
|
|
|
|
|
|
|
|
This option is primarily of use on a system where the headers in
|
2012-02-28 14:44:20 +00:00
|
|
|
`/usr/include' come from an older version of the GNU C Library.
|
|
|
|
|
Conflicts can occasionally happen in this case. You can also use
|
|
|
|
|
this option if you want to compile the GNU C Library with a newer
|
|
|
|
|
set of kernel headers than the ones found in `/usr/include'.
|
1998-05-18 09:53:46 +00:00
|
|
|
|
1998-11-04 23:04:21 +00:00
|
|
|
`--enable-add-ons[=LIST]'
|
2006-03-06 10:59:43 +00:00
|
|
|
Specify add-on packages to include in the build. If this option is
|
1999-09-05 23:34:47 +00:00
|
|
|
specified with no list, it enables all the add-on packages it
|
2006-03-06 10:59:43 +00:00
|
|
|
finds in the main source directory; this is the default behavior.
|
|
|
|
|
You may specify an explicit list of add-ons to use in LIST,
|
|
|
|
|
separated by spaces or commas (if you use spaces, remember to
|
|
|
|
|
quote them from the shell). Each add-on in LIST can be an
|
|
|
|
|
absolute directory name or can be a directory name relative to the
|
|
|
|
|
main source directory, or relative to the build directory (that
|
|
|
|
|
is, the current working directory). For example,
|
2012-02-21 01:01:28 +00:00
|
|
|
`--enable-add-ons=nptl,../glibc-libidn-VERSION'.
|
1998-05-18 09:53:46 +00:00
|
|
|
|
2000-11-04 03:29:28 +00:00
|
|
|
`--enable-kernel=VERSION'
|
2002-08-22 00:13:04 +00:00
|
|
|
This option is currently only useful on GNU/Linux systems. The
|
2000-11-04 03:29:28 +00:00
|
|
|
VERSION parameter should have the form X.Y.Z and describes the
|
|
|
|
|
smallest version of the Linux kernel the generated library is
|
|
|
|
|
expected to support. The higher the VERSION number is, the less
|
|
|
|
|
compatibility code is added, and the faster the code gets.
|
|
|
|
|
|
1998-05-18 09:53:46 +00:00
|
|
|
`--with-binutils=DIRECTORY'
|
|
|
|
|
Use the binutils (assembler and linker) in `DIRECTORY', not the
|
2002-04-06 01:45:15 +00:00
|
|
|
ones the C compiler would default to. You can use this option if
|
1998-05-18 09:53:46 +00:00
|
|
|
the default binutils on your system cannot deal with all the
|
2012-02-28 14:44:20 +00:00
|
|
|
constructs in the GNU C Library. In that case, `configure' will
|
1999-09-05 23:34:47 +00:00
|
|
|
detect the problem and suppress these constructs, so that the
|
|
|
|
|
library will still be usable, but functionality may be lost--for
|
|
|
|
|
example, you can't build a shared libc with old binutils.
|
1998-05-18 09:53:46 +00:00
|
|
|
|
|
|
|
|
`--without-fp'
|
|
|
|
|
Use this option if your computer lacks hardware floating-point
|
|
|
|
|
support and your operating system does not emulate an FPU.
|
|
|
|
|
|
|
|
|
|
`--disable-shared'
|
1999-09-05 23:34:47 +00:00
|
|
|
Don't build shared libraries even if it is possible. Not all
|
|
|
|
|
systems support shared libraries; you need ELF support and
|
|
|
|
|
(currently) the GNU linker.
|
1998-05-18 09:53:46 +00:00
|
|
|
|
|
|
|
|
`--disable-profile'
|
1998-11-04 23:04:21 +00:00
|
|
|
Don't build libraries with profiling information. You may want to
|
|
|
|
|
use this option if you don't plan to do profiling.
|
1998-05-18 09:53:46 +00:00
|
|
|
|
1998-11-04 23:04:21 +00:00
|
|
|
`--enable-static-nss'
|
|
|
|
|
Compile static versions of the NSS (Name Service Switch) libraries.
|
|
|
|
|
This is not recommended because it defeats the purpose of NSS; a
|
|
|
|
|
program linked statically with the NSS libraries cannot be
|
|
|
|
|
dynamically reconfigured to use a different name database.
|
|
|
|
|
|
2002-02-07 06:38:57 +00:00
|
|
|
`--without-tls'
|
2002-04-06 01:45:15 +00:00
|
|
|
By default the C library is built with support for thread-local
|
2002-02-07 06:38:57 +00:00
|
|
|
storage if the used tools support it. By using `--without-tls'
|
|
|
|
|
this can be prevented though there generally is no reason since it
|
|
|
|
|
creates compatibility problems.
|
|
|
|
|
|
2013-03-13 01:25:40 +00:00
|
|
|
`--enable-hardcoded-path-in-tests'
|
|
|
|
|
By default, dynamic tests are linked to run with the installed C
|
|
|
|
|
library. This option hardcodes the newly built C library path in
|
|
|
|
|
dynamic tests so that they can be invoked directly.
|
|
|
|
|
|
2013-05-17 02:17:14 +00:00
|
|
|
`--enable-lock-elision=yes'
|
2013-07-04 15:03:03 +00:00
|
|
|
Enable lock elision for pthread mutexes by default.
|
2013-05-17 02:17:14 +00:00
|
|
|
|
2013-07-19 06:42:03 +00:00
|
|
|
`--enable-pt_chown'
|
|
|
|
|
The file `pt_chown' is a helper binary for `grantpt' (*note
|
|
|
|
|
Pseudo-Terminals: Allocation.) that is installed setuid root to
|
|
|
|
|
fix up pseudo-terminal ownership. It is not built by default
|
|
|
|
|
because systems using the Linux kernel are commonly built with the
|
|
|
|
|
`devpts' filesystem enabled and mounted at `/dev/pts', which
|
|
|
|
|
manages pseudo-terminal ownership automatically. By using
|
|
|
|
|
`--enable-pt_chown', you may build `pt_chown' and install it
|
|
|
|
|
setuid and owned by `root'. The use of `pt_chown' introduces
|
|
|
|
|
additional security risks to the system and you should enable it
|
|
|
|
|
only if you understand and accept those risks.
|
|
|
|
|
|
1998-11-04 23:04:21 +00:00
|
|
|
`--build=BUILD-SYSTEM'
|
|
|
|
|
`--host=HOST-SYSTEM'
|
1999-09-05 23:34:47 +00:00
|
|
|
These options are for cross-compiling. If you specify both
|
|
|
|
|
options and BUILD-SYSTEM is different from HOST-SYSTEM, `configure'
|
2012-02-28 14:44:20 +00:00
|
|
|
will prepare to cross-compile the GNU C Library from BUILD-SYSTEM
|
|
|
|
|
to be used on HOST-SYSTEM. You'll probably need the
|
|
|
|
|
`--with-headers' option too, and you may have to override
|
|
|
|
|
CONFIGURE's selection of the compiler and/or binutils.
|
1998-11-04 23:04:21 +00:00
|
|
|
|
2002-04-06 01:45:15 +00:00
|
|
|
If you only specify `--host', `configure' will prepare for a
|
|
|
|
|
native compile but use what you specify instead of guessing what
|
2014-03-13 15:01:15 +00:00
|
|
|
your system is. This is most useful to change the CPU submodel.
|
2002-04-06 01:45:15 +00:00
|
|
|
For example, if `configure' guesses your machine as
|
2013-03-13 01:25:40 +00:00
|
|
|
`i686-pc-linux-gnu' but you want to compile a library for 586es,
|
|
|
|
|
give `--host=i586-pc-linux-gnu' or just `--host=i586-linux' and add
|
|
|
|
|
the appropriate compiler flags (`-mcpu=i586' will do the trick) to
|
1999-08-18 17:23:25 +00:00
|
|
|
CFLAGS.
|
1998-11-09 18:21:06 +00:00
|
|
|
|
2002-04-06 01:45:15 +00:00
|
|
|
If you specify just `--build', `configure' will get confused.
|
1998-05-18 09:53:46 +00:00
|
|
|
|
2012-11-09 22:13:45 +00:00
|
|
|
`--with-pkgversion=VERSION'
|
|
|
|
|
Specify a description, possibly including a build number or build
|
|
|
|
|
date, of the binaries being built, to be included in `--version'
|
|
|
|
|
output from programs installed with the GNU C Library. For
|
|
|
|
|
example, `--with-pkgversion='FooBar GNU/Linux glibc build 123''.
|
|
|
|
|
The default value is `GNU libc'.
|
|
|
|
|
|
|
|
|
|
`--with-bugurl=URL'
|
|
|
|
|
Specify the URL that users should visit if they wish to report a
|
|
|
|
|
bug, to be included in `--help' output from programs installed with
|
|
|
|
|
the GNU C Library. The default value refers to the main
|
|
|
|
|
bug-reporting information for the GNU C Library.
|
|
|
|
|
|
1998-05-18 09:53:46 +00:00
|
|
|
To build the library and related programs, type `make'. This will
|
|
|
|
|
produce a lot of output, some of which may look like errors from `make'
|
1998-11-04 23:04:21 +00:00
|
|
|
but isn't. Look for error messages from `make' containing `***'.
|
2002-04-06 01:45:15 +00:00
|
|
|
Those indicate that something is seriously wrong.
|
1998-05-18 09:53:46 +00:00
|
|
|
|
2006-03-06 10:59:43 +00:00
|
|
|
The compilation process can take a long time, depending on the
|
|
|
|
|
configuration and the speed of your machine. Some complex modules may
|
|
|
|
|
take a very long time to compile, as much as several minutes on slower
|
|
|
|
|
machines. Do not panic if the compiler appears to hang.
|
1998-11-04 23:04:21 +00:00
|
|
|
|
2002-02-07 06:38:57 +00:00
|
|
|
If you want to run a parallel make, simply pass the `-j' option with
|
|
|
|
|
an appropriate numeric parameter to `make'. You need a recent GNU
|
|
|
|
|
`make' version, though.
|
1999-09-05 23:34:47 +00:00
|
|
|
|
|
|
|
|
To build and run test programs which exercise some of the library
|
|
|
|
|
facilities, type `make check'. If it does not complete successfully,
|
|
|
|
|
do not use the built library, and report a bug after verifying that the
|
|
|
|
|
problem is not already known. *Note Reporting Bugs::, for instructions
|
|
|
|
|
on reporting bugs. Note that some of the tests assume they are not
|
2012-02-28 14:44:20 +00:00
|
|
|
being run by `root'. We recommend you compile and test the GNU C
|
|
|
|
|
Library as an unprivileged user.
|
1998-05-18 09:53:46 +00:00
|
|
|
|
2002-02-07 06:38:57 +00:00
|
|
|
Before reporting bugs make sure there is no problem with your system.
|
2002-04-06 01:45:15 +00:00
|
|
|
The tests (and later installation) use some pre-existing files of the
|
2002-02-07 06:38:57 +00:00
|
|
|
system such as `/etc/passwd', `/etc/nsswitch.conf' and others. These
|
|
|
|
|
files must all contain correct and sensible content.
|
|
|
|
|
|
Do not terminate default test runs on test failure.
This patch is an updated version of
<https://sourceware.org/ml/libc-alpha/2014-01/msg00198.html> and
<https://sourceware.org/ml/libc-alpha/2014-03/msg00180.html>.
Normal practice for software testsuites is that rather than
terminating immediately when a test fails, they continue running and
report at the end on how many tests passed or failed.
The principle behind the glibc testsuite stopping on failure was
probably that the expected state is no failures and so any failure
indicates a problem such as miscompilation. In practice, while this
is fairly close to true for native testing on x86_64 and x86 (kernel
bugs and race conditions can still cause intermittent failures), it's
less likely to be the case on other platforms, and so people testing
glibc run the testsuite with "make -k" and then examine the logs to
determine whether the failures are what they expect to fail on that
platform, possibly with some automation for the comparison.
This patch switches the glibc testsuite to the normal convention of
not stopping on failure - unless you use stop-on-test-failure=y, in
which case it behaves essentially as it did before (and does not
generate overall test summaries on failure). Instead, the summary
tests.sum may contain tests that FAILed. At the end of the test run,
any FAIL or ERROR lines from tests.sum are printed, and then it exits
with error status if there were any such lines. In addition, build
failures will also cause the test run to stop - this has the
justification that those *do* indicate serious problems that should be
promptly fixed and aren't generally hard to fix (but apart from that,
avoiding the build stopping on those failures seems harder).
Note that unlike the previous patches in this series, this *does*
require people with automation around testing glibc to change their
processes - either to start using tests.sum / xtests.sum to track
failures and compare them with expectations (with or without also
using "make -k" and examining "make" logs to identify build failures),
or else to use stop-on-test-failure=y and ignore the new tests.sum /
xtests.sum mechanism. (If all you check is the exit status from "make
check", no changes are needed unless you want to avoid test runs
continuing after the first failure.)
Tested x86_64.
* scripts/evaluate-test.sh: Handle fourth argument to determine
whether test run should stop on failure.
* Makeconfig (stop-on-test-failure): New variable.
(evaluate-test): Pass fourth argument to evaluate-test.sh based on
$(stop-on-test-failure).
* Makefile (tests): Give a summary of results from testing and
exit with failure status if they include an ERROR or FAIL.
(xtests): Likewise.
* manual/install.texi (Configuring and compiling): Mention
stop-on-test-failure=y.
* INSTALL: Regenerated.
2014-03-14 21:02:40 +00:00
|
|
|
Normally, `make check' will run all the tests before reporting all
|
|
|
|
|
problems found and exiting with error status if any problems occurred.
|
|
|
|
|
You can specify `stop-on-test-failure=y' when running `make check' to
|
|
|
|
|
make the test run stop and exit with an error status immediately when a
|
|
|
|
|
failure occurs.
|
|
|
|
|
|
1998-05-18 09:53:46 +00:00
|
|
|
To format the `GNU C Library Reference Manual' for printing, type
|
1998-11-09 18:21:06 +00:00
|
|
|
`make dvi'. You need a working TeX installation to do this. The
|
2012-05-16 18:50:39 +00:00
|
|
|
distribution builds the on-line formatted version of the manual, as
|
|
|
|
|
Info files, as part of the build process. You can build them manually
|
|
|
|
|
with `make info'.
|
1998-11-09 18:21:06 +00:00
|
|
|
|
2000-03-10 09:36:06 +00:00
|
|
|
The library has a number of special-purpose configuration parameters
|
|
|
|
|
which you can find in `Makeconfig'. These can be overwritten with the
|
|
|
|
|
file `configparms'. To change them, create a `configparms' in your
|
|
|
|
|
build directory and add values as appropriate for your system. The
|
|
|
|
|
file is included and parsed by `make' and has to follow the conventions
|
|
|
|
|
for makefiles.
|
|
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
It is easy to configure the GNU C Library for cross-compilation by
|
2000-03-10 09:36:06 +00:00
|
|
|
setting a few variables in `configparms'. Set `CC' to the
|
|
|
|
|
cross-compiler for the target you configured the library for; it is
|
|
|
|
|
important to use this same `CC' value when running `configure', like
|
|
|
|
|
this: `CC=TARGET-gcc configure TARGET'. Set `BUILD_CC' to the compiler
|
2002-04-06 01:45:15 +00:00
|
|
|
to use for programs run on the build system as part of compiling the
|
2012-01-07 16:29:31 +00:00
|
|
|
library. You may need to set `AR' to cross-compiling versions of `ar'
|
|
|
|
|
if the native tools are not configured to work with object files for
|
2012-10-25 19:17:45 +00:00
|
|
|
the target you configured for. When cross-compiling the GNU C Library,
|
|
|
|
|
it may be tested using `make check
|
|
|
|
|
test-wrapper="SRCDIR/scripts/cross-test-ssh.sh HOSTNAME"', where SRCDIR
|
|
|
|
|
is the absolute directory name for the main source directory and
|
|
|
|
|
HOSTNAME is the host name of a system that can run the newly built
|
|
|
|
|
binaries of the GNU C Library. The source and build directories must
|
|
|
|
|
be visible at the same locations on both the build system and HOSTNAME.
|
2000-03-10 09:36:06 +00:00
|
|
|
|
2012-10-31 20:43:54 +00:00
|
|
|
In general, when testing the GNU C Library, `test-wrapper' may be set
|
|
|
|
|
to the name and arguments of any program to run newly built binaries.
|
|
|
|
|
This program must preserve the arguments to the binary being run, its
|
Don't require test wrappers to preserve environment variables, use more consistent environment.
One wart in the original support for test wrappers for cross testing,
as noted in
<https://sourceware.org/ml/libc-alpha/2012-10/msg00722.html>, is the
requirement for test wrappers to pass a poorly-defined set of
environment variables from the build system to the system running the
glibc under test. Although some variables are passed explicitly via
$(test-wrapper-env), including LD_* variables that simply can't be
passed implicitly because of the side effects they'd have on the build
system's dynamic linker, others are passed implicitly, including
variables such as GCONV_PATH and LOCPATH that could potentially affect
the build system's libc (so effectively relying on any such effects
not breaking the wrappers). In addition, the code in
cross-test-ssh.sh for preserving environment variables is fragile (it
depends on how bash formats a list of exported variables, and could
well break for multi-line variable definitions where the contents
contain things looking like other variable definitions).
This patch moves to explicitly passing environment variables via
$(test-wrapper-env). Makefile variables that previously used
$(test-wrapper) are split up into -before-env and -after-env parts
that can be passed separately to the various .sh files used in
testing, so those files can then insert environment settings between
the two parts.
The common default environment settings in make-test-out are made into
a separate makefile variable that can also be passed to scripts,
rather than many scripts duplicating those settings (for testing an
installed glibc, it is desirable to have the GCONV_PATH setting on
just one place, so just that one place needs to support it pointing to
an installed sysroot instead of the build tree). The default settings
are included in the variables such as $(test-program-prefix), so that
if tests do not need any non-default settings they can continue to use
single variables rather than the split-up variables.
Although this patch cleans up LC_ALL=C settings (that being part of
the common defaults), various LANG=C and LANGUAGE=C settings remain.
Those are generally unnecessary and I propose a subsequent cleanup to
remove them. LC_ALL takes precedence over LANG, and while LANGUAGE
takes precedence over LC_ALL, it only does so for settings other than
LC_ALL=C. So LC_ALL=C on its own is sufficient to ensure the C
locale, and anything that gets LC_ALL=C does not need the other
settings.
While preparing this patch I noticed some tests with .sh files that
appeared to do nothing beyond what the generic makefile support for
tests can do (localedata/tst-wctype.sh - the makefiles support -ENV
variables and .input files - and localedata/tst-mbswcs.sh - just runs
five tests that could be run individually from the makefile). So I
propose another subsequent cleanup to move those to using the generic
support instead of special .sh files.
Tested x86_64 (native) and powerpc32 (cross).
* Makeconfig (run-program-env): New variable.
(run-program-prefix-before-env): Likewise.
(run-program-prefix-after-env): Likewise.
(run-program-prefix): Define in terms of new variables.
(built-program-cmd-before-env): New variable.
(built-program-cmd-after-env): Likewise.
(built-program-cmd): Define in terms of new variables.
(test-program-prefix-before-env): New variable.
(test-program-prefix-after-env): Likewise.
(test-program-prefix): Define in terms of new variables.
(test-program-cmd-before-env): New variable.
(test-program-cmd-after-env): Likewise.
(test-program-cmd): Define in terms of new variables.
* Rules (make-test-out): Use $(run-program-env).
* scripts/cross-test-ssh.sh (env_blacklist): Remove variable.
(help): Do not mention environment variables. Mention
--timeoutfactor option.
(timeoutfactor): New variable.
(blacklist_exports): Remove function.
(exports): Remove variable.
(command): Do not include ${exports}.
* manual/install.texi (Configuring and compiling): Do not mention
test wrappers preserving environment variables. Mention that last
assignment to a variable must take precedence.
* INSTALL: Regenerated.
* benchtests/Makefile (run-bench): Use $(run-program-env).
* catgets/Makefile ($(objpfx)test1.cat): Use
$(built-program-cmd-before-env), $(run-program-env) and
$(built-program-cmd-after-env).
($(objpfx)test2.cat): Do not specify environment variables
explicitly.
($(objpfx)de/libc.cat): Use $(built-program-cmd-before-env),
$(run-program-env) and $(built-program-cmd-after-env).
($(objpfx)test-gencat.out): Use $(test-program-cmd-before-env),
$(run-program-env) and $(test-program-cmd-after-env).
($(objpfx)sample.SJIS.cat): Do not specify environment variables
explicitly.
* catgets/test-gencat.sh: Use test_program_cmd_before_env,
run_program_env and test_program_cmd_after_env arguments.
* elf/Makefile ($(objpfx)tst-pathopt.out): Use $(run-program-env).
* elf/tst-pathopt.sh: Use run_program_env argument.
* iconvdata/Makefile ($(objpfx)iconv-test.out): Use
$(test-wrapper-env) and $(run-program-env).
* iconvdata/run-iconv-test.sh: Use test_wrapper_env and
run_program_env arguments.
* iconvdata/tst-table.sh: Do not set GCONV_PATH explicitly.
* intl/Makefile ($(objpfx)tst-gettext.out): Use
$(test-program-prefix-before-env), $(run-program-env) and
$(test-program-prefix-after-env).
($(objpfx)tst-gettext2.out): Likewise.
* intl/tst-gettext.sh: Use test_program_prefix_before_env,
run_program_env and test_program_prefix_after_env arguments.
* intl/tst-gettext2.sh: Likewise.
* intl/tst-gettext4.sh: Do not set environment variables
explicitly.
* intl/tst-gettext6.sh: Likewise.
* intl/tst-translit.sh: Likewise.
* malloc/Makefile ($(objpfx)tst-mtrace.out): Use
$(test-program-prefix-before-env), $(run-program-env) and
$(test-program-prefix-after-env).
* malloc/tst-mtrace.sh: Use test_program_prefix_before_env,
run_program_env and test_program_prefix_after_env arguments.
* math/Makefile (run-regen-ulps): Use $(run-program-env).
* nptl/Makefile ($(objpfx)tst-tls6.out): Use $(run-program-env).
* nptl/tst-tls6.sh: Use run_program_env argument. Set LANG=C
explicitly with each use of ${test_wrapper_env}.
* posix/Makefile ($(objpfx)wordexp-tst.out): Use
$(test-program-prefix-before-env), $(run-program-env) and
$(test-program-prefix-after-env).
* posix/tst-getconf.sh: Do not set environment variables
explicitly.
* posix/wordexp-tst.sh: Use test_program_prefix_before_env,
run_program_env and test_program_prefix_after_env arguments.
* stdio-common/tst-printf.sh: Do not set environment variables
explicitly.
* stdlib/Makefile ($(objpfx)tst-fmtmsg.out): Use
$(test-program-prefix-before-env), $(run-program-env) and
$(test-program-prefix-after-env).
* stdlib/tst-fmtmsg.sh: Use test_program_prefix_before_env,
run_program_env and test_program_prefix_after_env arguments.
Split $test calls into $test_pre and $test.
* timezone/Makefile (build-testdata): Use
$(built-program-cmd-before-env), $(run-program-env) and
$(built-program-cmd-after-env).
localedata/ChangeLog:
* Makefile ($(addprefix $(objpfx),$(CTYPE_FILES))): Use
$(built-program-cmd-before-env), $(run-program-env) and
$(built-program-cmd-after-env).
($(objpfx)sort-test.out): Use $(test-program-prefix-before-env),
$(run-program-env) and $(test-program-prefix-after-env).
($(objpfx)tst-fmon.out): Use $(run-program-prefix-before-env),
$(run-program-env) and $(run-program-prefix-after-env).
($(objpfx)tst-locale.out): Use $(built-program-cmd-before-env),
$(run-program-env) and $(built-program-cmd-after-env).
($(objpfx)tst-trans.out): Use $(run-program-prefix-before-env),
$(run-program-env), $(run-program-prefix-after-env),
$(test-program-prefix-before-env) and
$(test-program-prefix-after-env).
($(objpfx)tst-ctype.out): Use $(test-program-cmd-before-env),
$(run-program-env) and $(test-program-cmd-after-env).
($(objpfx)tst-wctype.out): Likewise.
($(objpfx)tst-langinfo.out): Likewise.
($(objpfx)tst-langinfo-static.out): Likewise.
* gen-locale.sh: Use localedef_before_env, run_program_env and
localedef_after_env arguments.
* sort-test.sh: Use test_program_prefix_before_env,
run_program_env and test_program_prefix_after_env arguments.
* tst-ctype.sh: Use tst_ctype_before_env, run_program_env and
tst_ctype_after_env arguments.
* tst-fmon.sh: Use run_program_prefix_before_env, run_program_env
and run_program_prefix_after_env arguments.
* tst-langinfo.sh: Use tst_langinfo_before_env, run_program_env
and tst_langinfo_after_env arguments.
* tst-locale.sh: Use localedef_before_env, run_program_env and
localedef_after_env arguments.
* tst-mbswcs.sh: Do not set environment variables explicitly.
* tst-numeric.sh: Likewise.
* tst-rpmatch.sh: Likewise.
* tst-trans.sh: Use run_program_prefix_before_env,
run_program_env, run_program_prefix_after_env,
test_program_prefix_before_env and test_program_prefix_after_env
arguments.
* tst-wctype.sh: Use tst_wctype_before_env, run_program_env and
tst_wctype_after_env arguments.
2014-06-06 22:19:27 +00:00
|
|
|
working directory and the standard input, output and error file
|
|
|
|
|
descriptors. If `TEST-WRAPPER env' will not work to run a program with
|
|
|
|
|
environment variables set, then `test-wrapper-env' must be set to a
|
|
|
|
|
program that runs a newly built program with environment variable
|
|
|
|
|
assignments in effect, those assignments being specified as `VAR=VALUE'
|
|
|
|
|
before the name of the program to be run. If multiple assignments to
|
|
|
|
|
the same variable are specified, the last assignment specified must
|
|
|
|
|
take precedence.
|
2012-10-31 20:43:54 +00:00
|
|
|
|
2006-03-01 10:05:04 +00:00
|
|
|
Installing the C Library
|
|
|
|
|
========================
|
1998-05-18 09:53:46 +00:00
|
|
|
|
2004-08-10 05:10:38 +00:00
|
|
|
To install the library and its header files, and the Info files of the
|
|
|
|
|
manual, type `env LANGUAGE=C LC_ALL=C make install'. This will build
|
|
|
|
|
things, if necessary, before installing them; however, you should still
|
2012-02-28 14:44:20 +00:00
|
|
|
compile everything first. If you are installing the GNU C Library as
|
|
|
|
|
your primary C library, we recommend that you shut the system down to
|
|
|
|
|
single-user mode first, and reboot afterward. This minimizes the risk
|
|
|
|
|
of breaking things when the library changes out from underneath.
|
1998-11-09 18:21:06 +00:00
|
|
|
|
2012-02-18 18:31:53 +00:00
|
|
|
`make install' will do the entire job of upgrading from a previous
|
2012-02-28 14:44:20 +00:00
|
|
|
installation of the GNU C Library version 2.x. There may sometimes be
|
|
|
|
|
headers left behind from the previous installation, but those are
|
|
|
|
|
generally harmless. If you want to avoid leaving headers behind you
|
|
|
|
|
can do things in the following order.
|
2000-03-10 09:36:06 +00:00
|
|
|
|
|
|
|
|
You must first build the library (`make'), optionally check it
|
|
|
|
|
(`make check'), switch the include directories and then install (`make
|
|
|
|
|
install'). The steps must be done in this order. Not moving the
|
|
|
|
|
directory before install will result in an unusable mixture of header
|
|
|
|
|
files from both libraries, but configuring, building, and checking the
|
|
|
|
|
library requires the ability to compile and run programs against the old
|
2012-02-18 18:31:53 +00:00
|
|
|
library. The new `/usr/include', after switching the include
|
|
|
|
|
directories and before installing the library should contain the Linux
|
|
|
|
|
headers, but nothing else. If you do this, you will need to restore
|
2012-02-28 14:44:20 +00:00
|
|
|
any headers from libraries other than the GNU C Library yourself after
|
|
|
|
|
installing the library.
|
2000-03-10 09:36:06 +00:00
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
You can install the GNU C Library somewhere other than where you
|
|
|
|
|
configured it to go by setting the `install_root' variable on the
|
|
|
|
|
command line for `make install'. The value of this variable is
|
|
|
|
|
prepended to all the paths for installation. This is useful when
|
|
|
|
|
setting up a chroot environment or preparing a binary distribution.
|
|
|
|
|
The directory should be specified with an absolute file name.
|
1998-11-09 18:21:06 +00:00
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
The GNU C Library includes a daemon called `nscd', which you may or
|
|
|
|
|
may not want to run. `nscd' caches name service lookups; it can
|
|
|
|
|
dramatically improve performance with NIS+, and may help with DNS as
|
|
|
|
|
well.
|
1998-11-09 18:21:06 +00:00
|
|
|
|
|
|
|
|
One auxiliary program, `/usr/libexec/pt_chown', is installed setuid
|
2013-09-10 04:09:27 +00:00
|
|
|
`root' if the `--enable-pt_chown' configuration option is used. This
|
|
|
|
|
program is invoked by the `grantpt' function; it sets the permissions
|
|
|
|
|
on a pseudoterminal so it can be used by the calling process. If you
|
|
|
|
|
are using a Linux kernel with the `devpts' filesystem enabled and
|
|
|
|
|
mounted at `/dev/pts', you don't need this program.
|
1998-05-18 09:53:46 +00:00
|
|
|
|
1999-09-05 23:34:47 +00:00
|
|
|
After installation you might want to configure the timezone and
|
2012-02-28 14:44:20 +00:00
|
|
|
locale installation of your system. The GNU C Library comes with a
|
1999-09-05 23:34:47 +00:00
|
|
|
locale database which gets configured with `localedef'. For example, to
|
|
|
|
|
set up a German locale with name `de_DE', simply issue the command
|
|
|
|
|
`localedef -i de_DE -f ISO-8859-1 de_DE'. To configure all locales
|
2012-02-28 14:44:20 +00:00
|
|
|
that are supported by the GNU C Library, you can issue from your build
|
|
|
|
|
directory the command `make localedata/install-locales'.
|
1999-09-05 23:34:47 +00:00
|
|
|
|
2002-04-06 01:45:15 +00:00
|
|
|
To configure the locally used timezone, set the `TZ' environment
|
|
|
|
|
variable. The script `tzselect' helps you to select the right value.
|
|
|
|
|
As an example, for Germany, `tzselect' would tell you to use
|
1999-09-05 23:34:47 +00:00
|
|
|
`TZ='Europe/Berlin''. For a system wide installation (the given paths
|
|
|
|
|
are for an installation with `--prefix=/usr'), link the timezone file
|
|
|
|
|
which is in `/usr/share/zoneinfo' to the file `/etc/localtime'. For
|
|
|
|
|
Germany, you might execute `ln -s /usr/share/zoneinfo/Europe/Berlin
|
|
|
|
|
/etc/localtime'.
|
|
|
|
|
|
2006-03-01 10:05:04 +00:00
|
|
|
Recommended Tools for Compilation
|
|
|
|
|
=================================
|
1998-05-18 09:53:46 +00:00
|
|
|
|
2004-08-10 05:10:38 +00:00
|
|
|
We recommend installing the following GNU tools before attempting to
|
2012-02-28 14:44:20 +00:00
|
|
|
build the GNU C Library:
|
1998-05-18 09:53:46 +00:00
|
|
|
|
2000-08-09 07:12:30 +00:00
|
|
|
* GNU `make' 3.79 or newer
|
1998-05-18 09:53:46 +00:00
|
|
|
|
|
|
|
|
You need the latest version of GNU `make'. Modifying the GNU C
|
1999-09-05 23:34:47 +00:00
|
|
|
Library to work with other `make' programs would be so difficult
|
|
|
|
|
that we recommend you port GNU `make' instead. *Really.* We
|
2002-04-06 01:45:15 +00:00
|
|
|
recommend GNU `make' version 3.79. All earlier versions have
|
|
|
|
|
severe bugs or lack features.
|
1998-05-18 09:53:46 +00:00
|
|
|
|
2013-06-26 23:10:48 +00:00
|
|
|
* GCC 4.4 or newer, GCC 4.6 recommended
|
2012-02-27 23:07:59 +00:00
|
|
|
|
2013-06-26 23:10:48 +00:00
|
|
|
GCC 4.4 or higher is required; as of this writing, GCC 4.6 is the
|
2012-02-28 14:44:20 +00:00
|
|
|
compiler we advise to use to build the GNU C Library.
|
1999-03-10 16:08:03 +00:00
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
You can use whatever compiler you like to compile programs that use
|
|
|
|
|
the GNU C Library.
|
1998-05-18 09:53:46 +00:00
|
|
|
|
2002-08-22 00:13:04 +00:00
|
|
|
Check the FAQ for any special compiler issues on particular
|
|
|
|
|
platforms.
|
1998-11-30 16:42:19 +00:00
|
|
|
|
2012-03-01 21:23:57 +00:00
|
|
|
* GNU `binutils' 2.20 or later
|
1998-05-18 09:53:46 +00:00
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
You must use GNU `binutils' (as and ld) to build the GNU C Library.
|
2004-02-29 19:50:54 +00:00
|
|
|
No other assembler or linker has the necessary functionality at the
|
2012-01-07 16:29:31 +00:00
|
|
|
moment.
|
1998-05-18 09:53:46 +00:00
|
|
|
|
2012-05-16 18:50:39 +00:00
|
|
|
* GNU `texinfo' 4.5 or later
|
1998-05-18 09:53:46 +00:00
|
|
|
|
|
|
|
|
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
|
1998-11-09 18:21:06 +00:00
|
|
|
installation mechanism for the info files is not present or works
|
1998-05-18 09:53:46 +00:00
|
|
|
differently.
|
|
|
|
|
|
2013-06-24 16:16:41 +00:00
|
|
|
* GNU `awk' 3.1.2, or higher
|
1998-11-04 23:04:21 +00:00
|
|
|
|
2013-06-24 16:16:41 +00:00
|
|
|
`awk' is used in several places to generate files. Some `gawk'
|
|
|
|
|
extensions are used, including the `asorti' function, which was
|
|
|
|
|
introduced in version 3.1.2 of `gawk'.
|
1998-05-18 09:53:46 +00:00
|
|
|
|
1998-11-04 23:04:21 +00:00
|
|
|
* Perl 5
|
|
|
|
|
|
|
|
|
|
Perl is not required, but it is used if present to test the
|
|
|
|
|
installation. We may decide to use it elsewhere in the future.
|
1998-05-18 09:53:46 +00:00
|
|
|
|
2000-03-10 09:36:06 +00:00
|
|
|
* GNU `sed' 3.02 or newer
|
|
|
|
|
|
2002-04-06 01:45:15 +00:00
|
|
|
`Sed' is used in several places to generate files. Most scripts
|
2000-03-10 09:36:06 +00:00
|
|
|
work with any version of `sed'. The known exception is the script
|
|
|
|
|
`po2test.sed' in the `intl' subdirectory which is used to generate
|
2002-04-06 01:45:15 +00:00
|
|
|
`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 `sed'.
|
2000-03-10 09:36:06 +00:00
|
|
|
|
1999-08-15 16:50:20 +00:00
|
|
|
|
2013-10-30 03:20:52 +00:00
|
|
|
If you change any of the `configure.ac' files you will also need
|
1998-05-18 09:53:46 +00:00
|
|
|
|
2004-02-29 19:50:54 +00:00
|
|
|
* GNU `autoconf' 2.53 or higher
|
1998-05-18 09:53:46 +00:00
|
|
|
|
|
|
|
|
and if you change any of the message translation files you will need
|
|
|
|
|
|
2001-04-19 20:15:22 +00:00
|
|
|
* GNU `gettext' 0.10.36 or later
|
1998-05-18 09:53:46 +00:00
|
|
|
|
|
|
|
|
You may also need these packages if you upgrade your source tree using
|
|
|
|
|
patches, although we try to avoid this.
|
|
|
|
|
|
2006-03-01 10:05:04 +00:00
|
|
|
Specific advice for GNU/Linux systems
|
|
|
|
|
=====================================
|
2004-08-10 05:10:38 +00:00
|
|
|
|
2012-03-08 01:27:38 +00:00
|
|
|
If you are installing the GNU C Library on GNU/Linux systems, you need
|
2014-04-30 15:39:30 +00:00
|
|
|
to have the header files from a 2.6.32 or newer kernel around for
|
2012-02-28 14:44:20 +00:00
|
|
|
reference. These headers must be installed using `make
|
|
|
|
|
headers_install'; the headers present in the kernel source directory
|
|
|
|
|
are not suitable for direct use by the GNU C Library. You do not need
|
|
|
|
|
to use that kernel, just have its headers installed where the GNU C
|
|
|
|
|
Library can access them, referred to here as INSTALL-DIRECTORY. The
|
|
|
|
|
easiest way to do this is to unpack it in a directory such as
|
|
|
|
|
`/usr/src/linux-VERSION'. In that directory, run `make headers_install
|
|
|
|
|
INSTALL_HDR_PATH=INSTALL-DIRECTORY'. Finally, configure the GNU C
|
|
|
|
|
Library with the option `--with-headers=INSTALL-DIRECTORY/include'.
|
|
|
|
|
Use the most recent kernel you can get your hands on. (If you are
|
|
|
|
|
cross-compiling the GNU C Library, you need to specify
|
|
|
|
|
`ARCH=ARCHITECTURE' in the `make headers_install' command, where
|
|
|
|
|
ARCHITECTURE is the architecture name used by the Linux kernel, such as
|
|
|
|
|
`x86' or `powerpc'.)
|
|
|
|
|
|
|
|
|
|
After installing the GNU C Library, you may need to remove or rename
|
2012-02-27 20:52:30 +00:00
|
|
|
directories such as `/usr/include/linux' and `/usr/include/asm', and
|
|
|
|
|
replace them with copies of directories such as `linux' and `asm' from
|
|
|
|
|
`INSTALL-DIRECTORY/include'. All directories present in
|
2012-02-28 14:44:20 +00:00
|
|
|
`INSTALL-DIRECTORY/include' should be copied, except that the GNU C
|
|
|
|
|
Library provides its own version of `/usr/include/scsi'; the files
|
|
|
|
|
provided by the kernel should be copied without replacing those
|
|
|
|
|
provided by the GNU C Library. The `linux', `asm' and `asm-generic'
|
|
|
|
|
directories are required to compile programs using the GNU C Library;
|
|
|
|
|
the other directories describe interfaces to the kernel but are not
|
|
|
|
|
required if not compiling programs using those interfaces. You do not
|
|
|
|
|
need to copy kernel headers if you did not specify an alternate kernel
|
|
|
|
|
header source using `--with-headers'.
|
|
|
|
|
|
2012-03-08 01:27:38 +00:00
|
|
|
The Filesystem Hierarchy Standard for GNU/Linux systems expects some
|
|
|
|
|
components of the GNU C Library installation to be in `/lib' and some
|
|
|
|
|
in `/usr/lib'. This is handled automatically if you configure the GNU
|
|
|
|
|
C Library with `--prefix=/usr'. If you set some other prefix or allow
|
|
|
|
|
it to default to `/usr/local', then all the components are installed
|
|
|
|
|
there.
|
1998-11-09 18:21:06 +00:00
|
|
|
|
2006-03-01 10:05:04 +00:00
|
|
|
Reporting Bugs
|
|
|
|
|
==============
|
1998-05-18 09:53:46 +00:00
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
There are probably bugs in the GNU C Library. There are certainly
|
1998-05-18 09:53:46 +00:00
|
|
|
errors and omissions in this manual. If you report them, they will get
|
|
|
|
|
fixed. If you don't, no one will ever know about them and they will
|
|
|
|
|
remain unfixed for all eternity, if not longer.
|
|
|
|
|
|
1999-09-05 23:34:47 +00:00
|
|
|
It is a good idea to verify that the problem has not already been
|
|
|
|
|
reported. Bugs are documented in two places: The file `BUGS' describes
|
2012-11-09 22:13:45 +00:00
|
|
|
a number of well known bugs and the central GNU C Library bug tracking
|
|
|
|
|
system has a WWW interface at `http://sourceware.org/bugzilla/'. The
|
|
|
|
|
WWW interface gives you access to open and closed reports. A closed
|
|
|
|
|
report normally includes a patch or a hint on solving the problem.
|
2002-04-06 01:45:15 +00:00
|
|
|
|
|
|
|
|
To report a bug, first you must find it. With any luck, this will
|
|
|
|
|
be the hard part. Once you've found a bug, make sure it's really a
|
2012-02-28 14:44:20 +00:00
|
|
|
bug. A good way to do this is to see if the GNU C Library behaves the
|
2002-04-06 01:45:15 +00:00
|
|
|
same way some other C library does. If so, probably you are wrong and
|
|
|
|
|
the libraries are right (but not necessarily). If not, one of the
|
2012-02-28 14:44:20 +00:00
|
|
|
libraries is probably wrong. It might not be the GNU C Library. Many
|
2002-04-06 01:45:15 +00:00
|
|
|
historical Unix C libraries permit things that we don't, such as
|
|
|
|
|
closing a file twice.
|
1998-11-09 18:21:06 +00:00
|
|
|
|
2012-02-28 14:44:20 +00:00
|
|
|
If you think you have found some way in which the GNU C Library does
|
1998-11-09 18:21:06 +00:00
|
|
|
not conform to the ISO and POSIX standards (*note Standards and
|
2000-03-10 09:36:06 +00:00
|
|
|
Portability::), that is definitely a bug. Report it!
|
1998-05-18 09:53:46 +00:00
|
|
|
|
|
|
|
|
Once you're sure you've found a bug, try to narrow it down to the
|
|
|
|
|
smallest test case that reproduces the problem. In the case of a C
|
|
|
|
|
library, you really only need to narrow it down to one library function
|
|
|
|
|
call, if possible. This should not be too difficult.
|
|
|
|
|
|
|
|
|
|
The final step when you have a simple test case is to report the bug.
|
2012-11-09 22:13:45 +00:00
|
|
|
Do this at `http://www.gnu.org/software/libc/bugs.html'.
|
1998-05-18 09:53:46 +00:00
|
|
|
|
|
|
|
|
If you are not sure how a function should behave, and this manual
|
|
|
|
|
doesn't tell you, that's a bug in the manual. Report that too! If the
|
|
|
|
|
function's behavior disagrees with the manual, then either the library
|
|
|
|
|
or the manual has a bug, so report the disagreement. If you find any
|
2004-08-10 05:10:38 +00:00
|
|
|
errors or omissions in this manual, please report them to the bug
|
|
|
|
|
database. If you refer to specific sections of the manual, please
|
|
|
|
|
include the section names for easier identification.
|
