-Supported Configurations
-========================
-
- The GNU C Library currently supports configurations that match the
-following patterns:
-
- alpha-*-linux
- arm-*-linux
- arm-*-linuxaout
- arm-*-none
- iX86-*-gnu
- iX86-*-linux
- m68k-*-linux
- powerpc-*-linux
- sparc-*-linux
- sparc64-*-linux
-
- Former releases of this library (version 1.09.1 and perhaps earlier
-versions) used to run on the following configurations:
-
- alpha-dec-osf1
- alpha-*-linuxecoff
- iX86-*-bsd4.3
- iX86-*-isc2.2
- iX86-*-isc3.N
- iX86-*-sco3.2
- iX86-*-sco3.2v4
- iX86-*-sysv
- iX86-*-sysv4
- iX86-force_cpu386-none
- iX86-sequent-bsd
- i960-nindy960-none
- m68k-hp-bsd4.3
- m68k-mvme135-none
- m68k-mvme136-none
- m68k-sony-newsos3
- m68k-sony-newsos4
- m68k-sun-sunos4.N
- mips-dec-ultrix4.N
- mips-sgi-irix4.N
- sparc-sun-solaris2.N
- sparc-sun-sunos4.N
-
- Since no one has volunteered to test and fix these configurations,
-they are not supported at the moment. They probably don't compile;
-they definitely don't work anymore. Porting the library is not hard.
-If you are interested in doing a port, please contact the glibc
-maintainers by sending electronic mail to <bug-glibc@gnu.org>.
-
- Valid cases of `iX86' include `i386', `i486', `i586', and `i686'.
-All of those configurations produce a library that can run on this
-processor and newer processors. The GCC compiler by default generates
-code that's optimized for the machine it's configured for and will use
-the instructions available on that machine. For example if your GCC is
-configured for `i686', gcc will optimize for `i686' and might issue
-some `i686' specific instructions. To generate code for other models,
-you have to configure for that model and give GCC the appropriate
-`-march=' and `-mcpu=' compiler switches via CFLAGS.
-
-Specific advice for Linux systems
-=================================
-
- If you are installing GNU libc on a Linux system, you need to have
-the header files from a 2.2 kernel around for reference. You do not
-need to use the 2.2 kernel, just have its headers where glibc can access
-at them. The easiest way to do this is to unpack it in a directory
-such as `/usr/src/linux-2.2.1'. In that directory, run `make config'
-and accept all the defaults. Then run `make include/linux/version.h'.
-Finally, configure glibc with the option
-`--with-headers=/usr/src/linux-2.2.1/include'. Use the most recent
-kernel you can get your hands on.
-
- An alternate tactic is to unpack the 2.2 kernel and run `make
-config' as above. Then rename or delete `/usr/include', create a new
-`/usr/include', and make the usual symbolic links of
-`/usr/include/linux' and `/usr/include/asm' into the 2.2 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.
-
- Note that `/usr/include/net' and `/usr/include/scsi' should *not* be
-symlinks into the kernel sources. GNU libc provides its own versions
-of these files.
-
- Linux expects some components of the libc installation to be in
-`/lib' and some in `/usr/lib'. This is handled automatically if you
-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
-program.
+Specific advice for GNU/Linux systems
+=====================================
+
+If you are installing the GNU C Library on GNU/Linux systems, you need
+to have the header files from a 2.6.32 or newer kernel around for
+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
+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
+`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'.
+
+ 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.