1 This directory contains the version VERSION release of the GNU C Library.
2 Many bugs have been fixed since the last release.
3 Some bugs surely remain.
5 As of this release, the GNU C library is known to run on the following
9 i[3456]86-*-linux-gnu Linux-2.x on Intel
10 m68k-*-linux-gnu Linux-2.x on Motorola 680x0
11 alpha*-*-linux-gnu Linux-2.x on DEC Alpha
12 powerpc-*-linux-gnu Linux and MkLinux on PowerPC systems
13 sparc-*-linux-gnu Linux-2.x on SPARC
14 sparc64-*-linux-gnu Linux-2.x on UltraSPARC 64-bit
15 arm-*-none ARM standalone systems
16 arm-*-linux Linux-2.x on ARM
17 arm-*-linuxaout Linux-2.x on ARM using a.out binaries
18 mips*-*-linux-gnu Linux-2.x on MIPS
19 ia64-*-linux-gnu Linux-2.x on ia64
20 s390-*-linux-gnu Linux-2.x on IBM S/390
21 s390x-*-linux-gnu Linux-2.x on IBM S/390 64-bit
22 sh-*-linux-gnu Linux-2.x on Super Hitachi
23 cris-*-linux-gnu Linux-2.4+ on CRIS
25 Former releases of this library (version 1.09.1 and perhaps earlier
26 versions) used to run on the following configurations:
36 i[3456]86-force_cpu386-none
50 Since no one has volunteered to test and fix the above configurations,
51 these are not supported at the moment. It's expected that these don't
52 work anymore. Porting the library is not hard. If you are interested
53 in doing a port, please contact the glibc maintainers by sending
54 electronic mail to <bug-glibc@gnu.org>.
56 There are some add-ons which can be used together with GNU libc. They
57 are designed in a way to ease the installation by integrating them in
58 the libc source tree. Simply get the add-ons you need and use the
59 --enable-add-ons option of the `configure' script to tell where the
60 add-ons are found. Please read the FAQ file for more details.
62 See the file INSTALL to find out how to configure, build, install, and port
63 the GNU C library. You might also consider reading the WWW pages for the
64 GNU libc at http://www.gnu.org/software/libc/libc.html.
66 The GNU C Library is completely documented by the Texinfo manual found
67 in the `manual/' subdirectory. The manual is still being updated and
68 contains some known errors and omissions; we regret that we do not
69 have the resources to work on the manual as much as we would like.
70 Please send comments on the manual to <bug-glibc-manual@gnu.org>, and
71 not to the library bug-reporting address.
73 The file NOTES contains a description of the feature-test macros used
74 in the GNU C library, explaining how you can tell the library what
75 facilities you want it to make available.
77 We prefer to get bug reports sent using the `glibcbug' shell script which
78 is installed together with the rest of the GNU libc to <bugs@gnu.org>.
79 Simply run this shell script and fill in the information. Nevertheless
80 you can still send bug reports to <bug-glibc@gnu.org> as normal electronic
83 The GNU C Library is free software. See the file COPYING.LIB for copying
84 conditions, and LICENSES for notices about a few contributions that require
85 these additional notices to be distributed.