aboutsummaryrefslogtreecommitdiff
path: root/manual
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>2000-07-05 22:34:10 +0000
committerUlrich Drepper <drepper@redhat.com>2000-07-05 22:34:10 +0000
commit11b3488225fff62fe08631c3d2a2d2ec6c48d90c (patch)
tree06335438eb3da12bbc5d0d2d0d86f02a17c2a926 /manual
parentf3e29a1a0f56035dcc343afea952dd8c0d4f42d0 (diff)
downloadglibc-11b3488225fff62fe08631c3d2a2d2ec6c48d90c.zip
glibc-11b3488225fff62fe08631c3d2a2d2ec6c48d90c.tar.gz
glibc-11b3488225fff62fe08631c3d2a2d2ec6c48d90c.tar.bz2
Update.
* crypt/md5-crypt.c (__md5_crypt_r): Clear arrays the key and salt string got copied in. Patch by Solar Designer <solar@false.com>. 2000-07-05 Andreas Jaeger <aj@suse.de> * manual/install.texi (Installation): Update information about add-ons. (Configuring and compiling): Update for glibc 2.2. 2000-07-04 Andreas Jaeger <aj@suse.de> * sysdeps/i386/fpu_control.h (_FPU_DEFAULT): Correct value. (_FPU_IEEE): Likewise. * math/Makefile (tests): Add test-fpucw. * math/test-fpucw.c (main): New file. 2000-07-05 Ulrich Drepper <drepper@redhat.com>
Diffstat (limited to 'manual')
-rw-r--r--manual/install.texi10
1 files changed, 5 insertions, 5 deletions
diff --git a/manual/install.texi b/manual/install.texi
index dbbd2cc..9bb4e64 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -15,9 +15,9 @@ Features can be added to GNU Libc via @dfn{add-on} bundles. These are
separate tarfiles which you unpack into the top level of the source
tree. Then you give @code{configure} the @samp{--enable-add-ons} option
to activate them, and they will be compiled into the library. As of the
-2.1 release, two important components of glibc are distributed as
-``official'' add-ons. Unless you are doing an unusual installation, you
-should get them both.
+2.2 release, one important component of glibc is distributed as
+``official'' add-ons: the linuxthreads add-on. Unless you are doing an
+unusual installation, you should get this.
Support for POSIX threads is maintained by someone else, so it's in a
separate package. It is only available for Linux systems, but this will
@@ -43,7 +43,7 @@ GNU Make, and possibly others. @xref{Tools for Compilation}, below.
GNU libc can be compiled in the source directory, but we strongly advise to
build it in a separate build directory. For example, if you have unpacked
-the glibc sources in @file{/src/gnu/glibc-2.1.0}, create a directory
+the glibc sources in @file{/src/gnu/glibc-2.2.0}, create a directory
@file{/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.
@@ -52,7 +52,7 @@ From your object directory, run the shell script @file{configure} found
at the top level of the source tree. In the scenario above, you'd type
@smallexample
-$ ../glibc-2.1.0/configure @var{args...}
+$ ../glibc-2.2.0/configure @var{args...}
@end smallexample
Please note that even if you're building in a separate build directory,