Remove documentation of upgrading from libc5.

1 files changed, 13 insertions, 29 deletions

diff --git a/INSTALL b/INSTALL
index 43a15ee..9f9588d 100644
--- a/INSTALL
+++ b/INSTALL
@@ -65,10 +65,9 @@ will be used, and CFLAGS sets optimization options for the compiler.
 
      This option is primarily of use on a system where the headers in
      `/usr/include' come from an older version of glibc.  Conflicts can
-     occasionally happen in this case.  Note that Linux libc5 qualifies
-     as an older version of glibc.  You can also use this option if you
-     want to compile glibc with a newer set of kernel headers than the
-     ones found in `/usr/include'.
+     occasionally happen in this case.  You can also use this option if
+     you want to compile glibc with a newer set of kernel headers than
+     the ones found in `/usr/include'.
 
 `--enable-add-ons[=LIST]'
      Specify add-on packages to include in the build.  If this option is
@@ -211,10 +210,11 @@ 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.
 
-   If you're upgrading from Linux libc5 or some other C library, you
-need to replace the `/usr/include' with a fresh directory before
-installing it.  The new `/usr/include' should contain the Linux
-headers, but nothing else.
+   `make install' will do the entire job of upgrading from a previous
+installation of glibc 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
@@ -222,20 +222,12 @@ 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 non-glibc libraries youself after installing the
 library.
 
-   If you are upgrading from a previous installation of glibc 2.0 or
-2.1, `make install' will do the entire job.  You do not need to remove
-the old includes - if you want to do so anyway you must then follow the
-order given above.
-
-   You may also need to reconfigure GCC to work with the new library.
-The easiest way to do that is to figure out the compiler switches to
-make it work again (`-Wl,--dynamic-linker=/lib/ld-linux.so.2' should
-work on GNU/Linux systems) and use them to recompile gcc.  You can also
-edit the specs file (`/usr/lib/gcc-lib/TARGET/VERSION/specs'), but that
-is a bit of a black art.
-
    You can install glibc 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
@@ -373,9 +365,7 @@ kernel you can get your hands on.
 config' as above; then, rename or delete `/usr/include', create a new
 `/usr/include', and make symbolic links of `/usr/include/linux' and
 `/usr/include/asm' into the kernel sources.  You can then configure
-glibc with no special options.  This tactic is recommended if you are
-upgrading from libc5, since you need to get rid of the old header files
-anyway.
+glibc with no special options.
 
    After installing GNU libc, you may need to remove or rename
 `/usr/include/linux' and `/usr/include/asm', and replace them with
@@ -398,12 +388,6 @@ configure glibc with `--prefix=/usr'.  If you set some other prefix or
 allow it to default to `/usr/local', then all the components are
 installed there.
 
-   If you are upgrading from libc5, you need to recompile every shared
-library on your system against the new library for the sake of new code,
-but keep the old libraries around for old binaries to use.  This is
-complicated and difficult.  Consult the Glibc2 HOWTO at
-`http://www.imaxx.net/~thrytis/glibc' for details.
-
    You cannot use `nscd' with 2.0 kernels, due to bugs in the
 kernel-side thread support.  `nscd' happens to hit these bugs
 particularly hard, but you might have problems with any threaded