-This directory contains the version 2.0.1 test release of the GNU C Library.
+This directory contains the version 2.3.4 release of the GNU C Library.
Many bugs have been fixed since the last release.
Some bugs surely remain.
configurations:
*-*-gnu GNU Hurd
- i[3456]86-*-linux-gnu Linux-2.0 on Intel
- m68k-*-linux-gnu Linux-2.0 on Motorola 680x0
- alpha-*-linux-gnu Linux-2.0 on DEC Alpha
-
-
-Former releases of this library (version 1.09.1 and perhaps earlier
-versions) used to run on the following configurations:
-
- alpha-dec-osf1
- i[3456]86-*-bsd4.3
- i[3456]86-*-isc2.2
- i[3456]86-*-isc3
- i[3456]86-*-sco3.2
- i[3456]86-*-sco3.2v4
- i[3456]86-*-sysv
- i[3456]86-*-sysv4
- i[3456]86-force_cpu386-none
- i[3456]86-sequent-bsd
- i960-nindy960-none
- m68k-hp-bsd4.3
- m68k-mvme135-none
- m68k-mvme136-none
- m68k-sony-newsos3
- m68k-sony-newsos4
- m68k-sun-sunos4
- mips-dec-ultrix4
- mips-sgi-irix4
- sparc-sun-solaris2
- sparc-sun-sunos4
-
-Whether this is still true for this release is unknown. Porting the
-library is not hard. If you are interested in doing a port, please
-get on the mailing list by sending electronic mail to
-<bug-glibc-request@prep.ai.mit.edu>.
-
-The GNU C library now includes Michael Glad's Ultra Fast Crypt, which
-provides the Unix `crypt' function, plus some other entry points.
-Because of the United States export restriction on DES implementations,
-we are distributing this code separately from the rest of the C
-library. There is an extra distribution tar file just for crypt; it is
-called `glibc-crypt-2.0.1.tar.gz'. You can just unpack the crypt
-distribution along with the rest of the C library and build; you can
-also build the library without getting crypt. Users outside the USA
-can get the crypt distribution via anonymous FTP from ftp.ifi.uio.no
-[129.240.64.21], or another archive site outside the USA. Archive
-maintainers are encouraged to copy this distribution to their archives
-outside the USA. Please get it from ftp.ifi.uio.no; transferring this
-distribution from prep.ai.mit.edu (or any other site in the USA) to a
-site outside the USA is in violation of US export laws.
-
-Beside the separate crypt tar file there are some more add-ons which can be
-used together with GNU libc. They are designed in a way to ease the
-installation by integrating them in the libc source tree. Simply get the
-add-ons you need and use the --enable-add-ons option of the `configure'
-script to tell where the add-ons are found. Please read the FAQ file for
-more details.
+ i[3456]86-*-linux-gnu Linux-2.x on Intel
+ m68k-*-linux-gnu Linux-2.x on Motorola 680x0
+ alpha*-*-linux-gnu Linux-2.x on DEC Alpha
+ powerpc-*-linux-gnu Linux and MkLinux on PowerPC systems
+ powerpc64-*-linux-gnu Linux-2.4.19+ on 64-bit PowerPC systems
+ sparc-*-linux-gnu Linux-2.x on SPARC
+ sparc64-*-linux-gnu Linux-2.x on UltraSPARC 64-bit
+ arm-*-none ARM standalone systems
+ arm-*-linux Linux-2.x on ARM
+ arm-*-linuxaout Linux-2.x on ARM using a.out binaries
+ mips*-*-linux-gnu Linux-2.x on MIPS
+ ia64-*-linux-gnu Linux-2.x on ia64
+ s390-*-linux-gnu Linux-2.x on IBM S/390
+ s390x-*-linux-gnu Linux-2.4+ on IBM S/390 64-bit
+ sh-*-linux-gnu Linux-2.x on Super Hitachi
+ x86-64-*-linux-gnu Linux-2.4+ on x86-64
+
+Past releases of this library ran on a variety of configurations that are
+no longer supported. Porting the library is not hard. If you are
+interested in doing a port, please contact the glibc maintainers;
+see http://www.gnu.org/software/libc/ for more information.
+
+There are some add-ons which can be used together with GNU libc. They
+are designed in a way to ease the installation by integrating them in
+the libc source tree. Simply get the add-ons you need and use the
+--enable-add-ons option of the `configure' script to tell where the
+add-ons are found. Please read the FAQ file for more details.
See the file INSTALL to find out how to configure, build, install, and port
the GNU C library. You might also consider reading the WWW pages for the
The GNU C Library is completely documented by the Texinfo manual found
in the `manual/' subdirectory. The manual is still being updated and
-contains some known errors and omissions; we regret that we do not have
-the resources to work on the manual as much as we would like. Please
-send comments on the manual to <bug-glibc-manual@prep.ai.mit.edu>, and
+contains some known errors and omissions; we regret that we do not
+have the resources to work on the manual as much as we would like.
+Please send comments on the manual to <bug-glibc-manual@gnu.org>, and
not to the library bug-reporting address.
The file NOTES contains a description of the feature-test macros used
in the GNU C library, explaining how you can tell the library what
facilities you want it to make available.
-We prefer to get bug reports sent using the `glibcbug' shell script which
-is install together with the rest of the GNU libc to <bugs@gnu.ai.mit.edu>.
-Simply run this shell script and fill in the information. Nevertheless
-you can still send bug reports to <bug-glibc@prep.ai.mit.edu> as normal
-electronic mails.
+Please see http://www.gnu.org/software/libc/bugs.html for bug reporting
+information. We are now using the Bugzilla system to track all bug reports.
+This web page gives detailed information on how to report bugs properly.
The GNU C Library is free software. See the file COPYING.LIB for copying
-conditions.
+conditions, and LICENSES for notices about a few contributions that require
+these additional notices to be distributed.