GNU C Library

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

GNU C Library
Heckert GNU white.svg
Original author(s) Roland McGrath
Developer(s) GNU Project
Initial release 1987; 37 years ago (1987)[1]
Stable release 2.23 (February 19, 2016; 8 years ago (2016-02-19)[2]) [±]
Development status Active
Written in C
Operating system Unix-like
Type Runtime library
License GNU Lesser General Public License
Website www.gnu.org/software/libc/
The Linux API is composed out of the System Call Interface of the Linux kernel, the GNU C Library (by GNU), libdrm, libalsa and libevdev (by freedesktop.org).
The GNU C Library is a wrapper around the system calls of the Linux kernel.
The Linux kernel and GNU C Library together form the Linux API. After compilation, the binaries offer an ABI.

The GNU C Library, commonly known as glibc, is the GNU Project's implementation of the C standard library. Despite its name, it now also directly supports C++ (and indirectly other programming languages). It was started in the early 1990s by the Free Software Foundation (FSF) for their GNU operating system.

Released under the GNU Lesser General Public License, glibc is free software.

History

The Glibc project was initially written mostly by Roland McGrath, working for the Free Software Foundation (FSF) in the 1980s.

In February 1988, FSF described glibc as having nearly completed the functionality required by ANSI C.[3] By 1992, it had the ANSI C-1989 and POSIX.1-1990 functions implemented and work was under way on POSIX.2.[4]

In September 1995 Ulrich Drepper did his first contribution to the glibc project and gradually became over the 1990s the core contributor and maintainer of glibc.[5] Drepper hold the maintainership position for many years and accumulated until 2012 63% of all commits of the project.[6]

Fork "Linux libc"

In the early 1990s, the developers of the Linux kernel forked glibc. Their fork, called "Linux libc", was maintained separately for years and released versions 2 through 5.

When FSF released glibc 2.0 in January 1997, it had much more complete POSIX standards compliance, better internationalisation and multilingual function, IPv6 capability, 64-bit data access, facilities for multithreaded applications, future version compatibility, and the code was more portable.[7] At this point, the Linux kernel developers discontinued their fork and returned to using FSF's glibc.[8]

The last used version of Linux libc used the internal name (soname) libc.so.5. Following on from this, glibc 2.x on Linux uses the soname libc.so.6[9] (Alpha and IA64 architectures now use libc.so.6.1, instead). The *.so file name is often abbreviated as libc6 (for example in the package name in Debian) following the normal conventions for libraries.

According to Richard Stallman, the changes that had been made in Linux libc could not be merged back into glibc because the authorship status of that code was unclear and the GNU project is quite strict about recording copyright and authors.[10]

Installation of a steering committee

Starting in 2001 the library's development had been overseen by a committee,[11] with Ulrich Drepper[12] kept as the lead contributor and maintainer. The steering committee installation was surrounded by a public controversy as it was openly described by Ulrich Drepper as failed hostile takeover maneuver by RMS.[13][14][15]

Switch to git

While before in a CVS repository, in 2009 glibc was migrated to a Git repository on Sourceware.[16]

Debian switches to EGLIBC

After long standing controversies around Drepper's leading style and external contribution acceptance,[17][18][19] Debian switched publicly to the glibc fork EGLIBC in 2009.[20]

Steering committee disbands

In March 2012, the steering committee voted to disband itself and remove Drepper in favor of a community-driven development process, with Ryan Arnold, Maxim Kuvyrkov, Joseph Myers, Carlos O'Donell, and Alexandre Oliva holding the responsibility of GNU maintainership (but no extra decision-making power).[21][22]

After the change in glibc maintainership Debian and other projects migrated back to the glibc, who before switched to alternatives.[23] Also, since the beginning of 2014, the glibc fork EGLIBC is no longer being developed, since its "goals are now being addressed directly in GLIBC".

Version history

For most systems, the version of glibc can be obtained by executing the lib file (for example, /lib/libc.so.6).

Functionality

glibc provides the functionality required by the Single UNIX Specification, POSIX (1c, 1d, and 1j) and some of the functionality required by ISO C11, ISO C99, Berkeley Unix (BSD) interfaces, the System V Interface Definition (SVID) and the X/Open Portability Guide (XPG), Issue 4.2, with all extensions common to XSI (X/Open System Interface) compliant systems along with all X/Open UNIX extensions.

In addition, glibc also provides extensions that have been deemed useful or necessary while developing GNU.

Supported hardware and kernels

Glibc is used in systems that run many different kernels and different hardware architectures. Its most common use is in systems using the Linux kernel on x86 hardware, however, officially supported hardware[24] includes: AArch64, ARM, DEC Alpha, PA-RISC, IA-64, Motorola m68k, MicroBlaze, MIPS, Nios II, PowerPC, s390, SPARC, TILE, and x86. It officially supports the Hurd and Linux kernels. Additionally, there are heavily patched versions that run on the kernels of FreeBSD and NetBSD (from which Debian GNU/kFreeBSD and Debian GNU/NetBSD systems are built, respectively), as well as a forked-version of OpenSolaris.[25] It is also used (in an edited form) and named libroot.so in BeOS and Haiku.[26]

Use in small devices

glibc has been criticized as being "bloated" and slower than other libraries in the past, e.g. by Linus Torvalds[27] and embedded Linux programmers. For this reason, several alternative C standard libraries have been created which emphasize a smaller footprint. Alternative libcs are Bionic (based mostly on libc from BSD and used in Android[28]), dietlibc, uClibc, Newlib, Klibc, and musl.

However, many small-device projects use GNU libc over the smaller alternatives because of its application support, standards compliance, and completeness. Examples include Openmoko[29] and Familiar Linux for iPaq handhelds (when using the GPE display software).[30]

Alternatives

Other C standard libraries as alternative to the GNU C Library are for instance: Bionic libc, dietlibc, EGLIBC, klibc, musl, Newlib, and uClibc.

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. glibc changelog on GitHub.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. rms-accused-of-attempting-glibc-hostile-takeover on slashdot.com on August 19, 2001
  16. glibc repo on Sourceware.com
  17. Ulrich Drepper 2007-10-03 06:13:55 UTC "This has nothing to do with "x86 only". All ABIs designed by people who have a bit of understanding require no change. Any change will negatively impact well designed architectures for the sole benefit of this embedded crap. But your own version of the file in the add-on."
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.

External links