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
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
20 Former releases of this library (version 1.09.1 and perhaps earlier
21 versions) used to run on the following configurations:
31 i[3456]86-force_cpu386-none
45 Since no one has volunteered to test and fix the above configurations,
46 these are not supported at the moment. It's expected that these don't
47 work anymore. Porting the library is not hard. If you are interested
48 in doing a port, please contact the glibc maintainers by sending
49 electronic mail to <bug-glibc@gnu.org>.
51 There are some add-ons which can be used together with GNU libc. They
52 are designed in a way to ease the installation by integrating them in
53 the libc source tree. Simply get the add-ons you need and use the
54 --enable-add-ons option of the `configure' script to tell where the
55 add-ons are found. Please read the FAQ file for more details.
57 See the file INSTALL to find out how to configure, build, install, and port
58 the GNU C library. You might also consider reading the WWW pages for the
59 GNU libc at http://www.gnu.org/software/libc/libc.html.
61 The GNU C Library is completely documented by the Texinfo manual found
62 in the `manual/' subdirectory. The manual is still being updated and
63 contains some known errors and omissions; we regret that we do not
64 have the resources to work on the manual as much as we would like.
65 Please send comments on the manual to <bug-glibc-manual@gnu.org>, and
66 not to the library bug-reporting address.
68 The file NOTES contains a description of the feature-test macros used
69 in the GNU C library, explaining how you can tell the library what
70 facilities you want it to make available.
72 We prefer to get bug reports sent using the `glibcbug' shell script which
73 is installed together with the rest of the GNU libc to <bugs@gnu.org>.
74 Simply run this shell script and fill in the information. Nevertheless
75 you can still send bug reports to <bug-glibc@gnu.org> as normal electronic
78 The GNU C Library is free software. See the file COPYING.LIB for copying