Configuring and compiling GNU Libc
==================================
- GNU Libc cannot be compiled in the source directory. You must
-create a separate directory for the object files. This directory
-should be outside the source tree. For example, if you have unpacked
+ GNU Libc can be compiled in the source directory but we'd advise to
+build in a separate build directory. For example, if you have unpacked
the glibc sources in `/src/gnu/glibc-2.1.0', create a directory
`/src/gnu/glibc-build' to put the object files in.
permissions on a pseudoterminal so it can be used by the calling
process. This means programs like `xterm' and `screen' do not have to
be setuid to get a pty. (There may be other reasons why they need
-privileges.) If you are using a 2.1 Linux kernel with the `devptsfs'
-or `devfs' filesystems providing pty slaves, you don't need this
-program; otherwise you do. The source for `pt_chown' is in
+privileges.) If you are using a 2.1 or newer Linux kernel with the
+`devptsfs' or `devfs' filesystems providing pty slaves, you don't need
+this program; otherwise you do. The source for `pt_chown' is in
`login/programs/pt_chown.c'.
Recommended Tools for Compilation
-This directory contains the version 2.0.112 test release of the GNU C Library.
+This directory contains the version 2.1 release of the GNU C Library.
Many bugs have been fixed since the last release.
Some bugs surely remain.
Because of the United States export restriction on DES implementations,
we are distributing this code separately from the rest of the C
library. There is an extra distribution tar file just for crypt; it is
-called `glibc-crypt-2.0.112.tar.gz'. You can just unpack the crypt
+called `glibc-crypt-2.1.tar.gz'. You can just unpack the crypt
distribution along with the rest of the C library and build; you can
also build the library without getting crypt. Users outside the USA
can get the crypt distribution via anonymous FTP from ftp.ifi.uio.no