-`--build=BUILD-SYSTEM'
-`--host=HOST-SYSTEM'
- These options are for cross-compiling. If you give them both and
- BUILD-SYSTEM is different from HOST-SYSTEM, `configure' will
- prepare to cross-compile glibc 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.
-
- If you give just one of these, `configure' will get confused. If
- `configure' doesn't correctly guess your system type for a native
- build, report that as a bug.
-
- 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'
-but isn't. Look for error messages from `make' containing `***'.
-Those indicate that something is really wrong.
-
- The compilation process takes several hours even on fast hardware.
-Expect at least two hours for the default configuration on i586 for
-Linux. For Hurd times are much longer. Except for EGCS 1.1 (and later
-versions of EGCS), all supported versions of GCC have a problem which
-causes them to take several minutes to compile certain files in the
-iconvdata directory. Do not panic if the compiler appears to hang.
-
- If you want to run a parallel make, you can't just give `make' the
-`-j' option, because it won't be passed down to the sub-makes.
-Instead, edit the generated `Makefile' and uncomment the line
-
- # PARALLELMFLAGS = -j 4
-
-You can change the `4' to some other number as appropriate for your
-system.
-
- To build and run some test programs which exercise some of the
-library facilities, type `make check'. This should complete
-successfully; if it doesn't, do not use the built library, and report a
-bug. *Note Reporting Bugs::, for how to do that. Note that some of
-the tests assume they are not being run by `root'. We recommend you
-compile and test glibc as an unprivileged user.
-
- To format the `GNU C Library Reference Manual' for printing, type
-`make dvi'. You need a working TeX installation to do this.
-
- To install the library and its header files, and the Info files of
-the manual, type `make install'. This will build things if necessary,
-before installing them. If you want to install the files in a different
-place than the one specified at configuration time you can specify a
-value for the Makefile variable `install_root' on the command line.
-This is useful to create chroot'ed environment or to prepare binary
-releases.
+'--without-tls'
+ By default the C library is built with support for thread-local
+ 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.
+
+'--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.
+
+'--enable-lock-elision=yes'
+ Enable lock elision for pthread mutexes by default.
+
+'--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.
+
+'--disable-werror'
+ By default, the GNU C Library is built with '-Werror'. If you wish
+ to build without this option (for example, if building with a newer
+ version of GCC than this version of the GNU C Library was tested
+ with, so new warnings cause the build with '-Werror' to fail), you
+ can configure with '--disable-werror'.
+
+'--build=BUILD-SYSTEM'
+'--host=HOST-SYSTEM'
+ These options are for cross-compiling. If you specify both options
+ and BUILD-SYSTEM is different from HOST-SYSTEM, 'configure' 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.
+
+ If you only specify '--host', 'configure' will prepare for a native
+ compile but use what you specify instead of guessing what your
+ system is. This is most useful to change the CPU submodel. For
+ example, if 'configure' guesses your machine as '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
+ CFLAGS.
+
+ If you specify just '--build', 'configure' will get confused.
+
+'--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.
+
+ 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'
+but isn't. Look for error messages from 'make' containing '***'. Those
+indicate that something is seriously wrong.
+
+ 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.
+
+ 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.
+
+ 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
+being run by 'root'. We recommend you compile and test the GNU C
+Library as an unprivileged user.
+
+ Before reporting bugs make sure there is no problem with your system.
+The tests (and later installation) use some pre-existing files of the
+system such as '/etc/passwd', '/etc/nsswitch.conf' and others. These
+files must all contain correct and sensible content.
+
+ 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.
+
+ To format the 'GNU C Library Reference Manual' for printing, type
+'make dvi'. You need a working TeX installation to do this. The
+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'.
+
+ 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.
+
+ It is easy to configure the GNU C Library for cross-compilation by
+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
+to use for programs run on the build system as part of compiling the
+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 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.
+
+ 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
+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.
+
+Installing the C Library
+========================
+
+To install the library and its header files, and the Info files of the
+manual, type 'make install'. This will build things, if necessary,
+before installing them; however, you should still 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.
+
+ 'make install' will do the entire job of upgrading from a previous
+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.
+
+ 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
+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 any
+headers from libraries other than the GNU C Library yourself after
+installing the library.
+
+ 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.
+
+ 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.
+
+ One auxiliary program, '/usr/libexec/pt_chown', is installed setuid
+'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.
+
+ After installation you might want to configure the timezone and
+locale installation of your system. The GNU C Library comes with a
+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 that
+are supported by the GNU C Library, you can issue from your build
+directory the command 'make localedata/install-locales'.
+
+ 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
+'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'.