Any Unix-like operating system needs a C library: the library which defines the ``system calls'' and other basic facilities such as open, malloc, printf, exit, etc. The GNU C library is used as the C library in the GNU system and most systems with the Linux kernel.
The GNU C library is primarily designed to be a portable and high performance C library. It follows all relevant standards (ISO C 99, POSIX.1c, POSIX.1j, POSIX.1d, Unix98, Single Unix Specification). It is also internationalized and has one of the most complete internationalization interfaces known.
This is a small developer oriented web page for glibc. Please look at the official FSF home page for glibc for more information.
2008-11-19: GLIBC 2.9 release tagged. Trunk is open for 2.10
2008-11-14: Pending 2.9 release
2008-04-21: GLIBC 2.8 ports add-on tagged
2008-04-11: GLIBC 2.8 release tagged
2008-04-09: Pending 2.8 release
Releases are available by CVS branch checkout only. For example, to download the 2.8 release, checkout the CVS libc module branch glibc-2_8-branch, and similarly for all required add-ons including ports.
Archives of the old glibc releases and pre-releases are available by anonymous ftp.
The FAQ, distributed in the source tree, is also available online.
You can access the development source tree a couple of different ways.
cvs -z 9 -d :pserver:anoncvs@sources.redhat.com:/cvs/glibc login
{enter "anoncvs" as the password}
cvs -z 9 -d :pserver:anoncvs@sources.redhat.com:/cvs/glibc co libc
To additionally fetch the contributed ports add-on:
cd libc cvs -z 9 -d :pserver:anoncvs@sources.redhat.com:/cvs/glibc co ports
If you have any questions about the contributed ports add-on please send email to libc-ports. Please do not send mail to libc-alpha.
You can use the cvsweb interface.
You can use git to check out the sources, including all revision history, with this command:
git clone git://sources.redhat.com/git/glibc.git
Please see the wiki for the most up to date information on the read-only git mirror.
Glibc has a bug database.
Got a problem? Want to know if you're the first to have it?
Check this database. The product name to use is glibc
.
Glibc has a wiki. Please feel free to add the community knowledge, feature wishlists, feature designs, debugging tips, or developer notes.
There are eight mailing lists regarding glibc hosted on sourceware.org:
libc-announce: The libc-anounce list is used to inform users and developers of upcoming releases and anouncements.
libc-alpha: The libc-alpha list is for the discussion of glibc development. Please do not ask for build help on this list.
libc-help: The libc-help list is intended for all glibc questions including build problems, C library usage, and more. No question about glibc is ever wrong on this list.
libc-hacker: Please note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
libc-locales: The libc-locals mailing list is used for discussing locale specific changes and patches to glibc.
libc-ports: The libc-ports mailing list is used by the add-on ports maintainers. Patches and discussion about the development of add-on ports should be sent to this list.
glibc-cvs, and glibc-bugs: The glibc-cvs and glibc-bugs lists exist solely to receive automated messages from CVS and from Bugzilla, respectively. Please do not post to these lists.
Mail archives are also available by anon-ftp in mbox formatted files.