GNU C library
GNU C library (glibc) is one of the most important components of GNU Hurd and most modern Linux distributions. It is used by almost all C programs and provides the most essential program interface.
| Tags | Software Development Libraries |
|---|---|
| Licenses | LGPL FDL GPL |
| Operating Systems | POSIX AIX GNU/Hurd Linux |
| Implementation | C |
Recent releases
- 28 May 2009 13:37
Changes: Several new interfaces were added. Faster strlen(), strchr(), strchrnul(), strrchr(), memchr(), and rawmemchr() functions were implemented for x86-64. The malloc implementation can be compiled to be less memory efficient but with higher performance in multi-threaded programs. A compile error for invalid C++ code when using the string function was resolved. Support for selecting between multiple function definitions at runtime was added. The libcrypt library can now use the hash function implementations in NSS. Two new locales were added.
- 24 Nov 2008 18:12
No changes have been submitted for this release.
- 19 Oct 2007 02:40
Changes: More checking functions were added: fread, fread_unlocked, open*, and mq_open. Fortification is extended to C++. An "m" modifier for scanf was added. C99/SUS compliance was made stricter by not recognizing "a" as a modifier when those specs are requested. New interfaces were added: mkostemp and mkostemp64. These are like mkstemp*, but allow additonal options to be passed. New Linux interfaces were added: signalfd, eventfd, eventfd_read, and eventfd_write. Private futexes are handled in the NPTL implementation. O_CLOEXEC is supported. Linux/x86-64 vDSO is supported. SHA-256 and SHA-512 based password encryption was implemented.
- 05 Nov 2005 22:33
Changes: GCC4 fixes.
- 20 Apr 2005 08:06
No changes have been submitted for this release.
- All comments
Recent commentsRe: How good is a release without tarball?
> Now, seriously, when will we see the
> next tarball release? Just
> a random CVS tag really is not good
> enough for such a vital
> system component. It's time to do the
> extra homework of
> putting a gold master release tarball
> up. Not only for comfort,
> but also for reference.
Agreed. This whole CVS only is crap. It should be a proper signed tarball that people can actually verify.
How good is a release without tarball?
Now, seriously, when will we see the next tarball release? Just
a random CVS tag really is not good enough for such a vital
system component. It's time to do the extra homework of
putting a gold master release tarball up. Not only for comfort,
but also for reference.
Re: Check Failing
>
> % I've had no trouble installing all
> the
> % nessary versions of everything (egcs,
> % binutils, etc) and the compliled and
> % installed fine. Glibc 2.1 complies
> fine
> % but when I "make check" it stopes at
> the
> % glob test in the postix directory.
> Any
> % know what would cause this?
>
>
> Yes, you probably have an earlier
> version of bash (pre 2.0.5? I think is
> the latest version). If you upgrade to
> the latest bash, globbing is fixed.
Mhh i used the latest bash while compiling glibc-2.3.3-20031202 and have the same trouble
ovis
Re: Upgrading from 2.1.3 to 2.3?
> Anyone got any links on upgrading from
> glibc 2.1.3 to 2.3? I want to upgrade my
> Red Hat Linux 6.2 system to 2.3 as the
> 2.1.3 it comes with is very old.
it's year late, but i just upgraded my hat 6.2 to glibc
2.3.2. i had to upgrade binutils to the most recent,
and had gcc 3.2.2. it went smoothly. the only
software i've found that quit working was a pre-
2000 version of wine that i need, and i've been
getting compilation errors about undefined reference
to 'errno.h'. thats all i know so far.
GLIBC 2.3.2 Compiling Weirdness
Ok. after 3-4 days of trying to figure out what is going on, I finally brought it down to this:
GLIBC 2.3.2 will not build from a build directory that looks like this: /build
But it will build without any problem in /setup/build
Anybody has a clue why? This one gets the weirdest compilation problem award...
GLIBC 2.3.1 does not have this problem.