Misplaced Pages

Glibc: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 02:11, 8 October 2013 edit70.198.1.174 (talk) Refined the infobox and citations. Implemented cite templates and refined some things.← Previous edit Revision as of 02:12, 8 October 2013 edit undoNasnema (talk | contribs)Extended confirmed users, Pending changes reviewers15,828 editsm Reverted edits by 70.198.1.174 (talk) to last revision by ScotXW (HG)Next edit →
Line 2: Line 2:
{{Redirect-distinguish|glibc|glib|gnulib}} {{Redirect-distinguish|glibc|glib|gnulib}}
{{Infobox software {{Infobox software
| name = GNU C Library | name = GNU C Library
| logo = ] | logo = ]
| author = Roland McGrath | author = Roland McGrath
| developer = ] | developer = ]
| released = {{Start date|df=yes|1987<!--|MM|DD|df=yes/no-->}}<ref>{{cite web|url=https://lwn.net/Articles/488847/|title=A turning point for GNU libc|last=Corbet|first=Jonathan|date=28 March 2012|publisher=LWN.net}}</ref> | released = {{Start date|df=yes|1987<!--|MM|DD|df=yes/no-->}}<ref>, By Jonathan Corbet, 28 March 2012, LWN.net</ref>
| status = Active | status = Active
| frequently updated = yes | frequently updated = yes
| operating system = ]
| programming language = ]
| operating system = ] | genre = ]
| genre = ] | license = ]
| license = ] | website = {{url|http://www.gnu.org/software/libc/}}
| website = {{url|http://www.gnu.org/software/libc/}}
}} }}
The '''GNU C Library''', commonly known as '''glibc''', is the ]'s implementation of the ]. Originally written by the ] (FSF) for the ] operating system, the library's development had been overseen by a committee since 2001,<ref>{{cite web The '''GNU C Library''', commonly known as '''glibc''', is the ]'s implementation of the ]. Originally written by the ] (FSF) for the ] operating system, the library's development had been overseen by a committee since 2001,<ref>{{cite web
Line 20: Line 19:
|quote=In 2001 The GNU C Library Steering Committee ..., was formed and currently consists of Mark Brown, Paul Eggert, Andreas Jaeger, Jakub Jelinek, Roland McGrath and Andreas Schwab. |quote=In 2001 The GNU C Library Steering Committee ..., was formed and currently consists of Mark Brown, Paul Eggert, Andreas Jaeger, Jakub Jelinek, Roland McGrath and Andreas Schwab.
}}</ref> with ]<ref>{{cite web|url=http://www.linkedin.com/in/ulrichdrepper |title=Ulrich Drepper |publisher=LinkedIn |date= |accessdate=2012-06-13}}</ref> as the lead contributor and maintainer. In March 2012, the steering committee voted to disband itself, in favor of a community-driven development process, with Ryan Arnold, Maxim Kuvyrkov, Joseph Myers, Carlos }}</ref> with ]<ref>{{cite web|url=http://www.linkedin.com/in/ulrichdrepper |title=Ulrich Drepper |publisher=LinkedIn |date= |accessdate=2012-06-13}}</ref> as the lead contributor and maintainer. In March 2012, the steering committee voted to disband itself, in favor of a community-driven development process, with Ryan Arnold, Maxim Kuvyrkov, Joseph Myers, Carlos
O'Donell, and ] as non-decision making project stewards.<ref>{{cite web|url=http://sourceware.org/ml/libc-alpha/2012-03/msg01038.html |last=McGrath |first=Roland |title=glibc steering committee dissolving |publisher=Sourceware.org |date=26 March 2012 |accessdate=2012-06-13}}</ref><ref>{{cite web|url=http://sourceware.org/ml/libc-alpha/2012-03/msg01040.html |last=Myers |first=Joseph S. |title=GNU C Library development and maintainers |publisher=Sourceware.org |date=26 March 2012 |accessdate=2012-06-13}}</ref> O'Donell, and ] as non-decision making project stewards.<ref>{{cite web|url=http://sourceware.org/ml/libc-alpha/2012-03/msg01038.html |author=Roland McGrath |title=glibc steering committee dissolving |publisher=Sourceware.org |date=26 March 2012 |accessdate=2012-06-13}}</ref><ref>{{cite web|url=http://sourceware.org/ml/libc-alpha/2012-03/msg01040.html |author=Joseph S. Myers |title=GNU C Library development and maintainers |publisher=Sourceware.org |date=26 March 2012 |accessdate=2012-06-13}}</ref>


Released under the ], glibc is ]. Released under the ], glibc is ].
Line 32: Line 31:
In the early 1990s, the developers of the ] ] glibc. Their fork, called "Linux libc", was maintained separately for years and released versions 2 through 5. In the early 1990s, the developers of the ] ] 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, ] capability, 64-bit data access, facilities for multithreaded applications, future version compatibility, and the code was more portable.<ref>{{cite web | url = http://people.redhat.com/~sopwith/old/glibc-vs-libc5.html | title = A Technical Comparison of glibc 2.x With Legacy System Libraries| last = Lee | first = Elliot | year = 2001 |archiveurl = http://web.archive.org/web/20040411191201/http://people.redhat.com/~sopwith/old/glibc-vs-libc5.html |archivedate = 11 April 2004}}</ref> At this point, the Linux kernel developers discontinued their fork and returned to using FSF's glibc.<ref>{{cite web | url = http://www.linux.com/archive/feature/3874 | title = Forking: it could even happen to you | quote = the split between GNU LIBC and the Linux LIBC -- it went on for years while Linux stabilized, and then the forks re-merged into one project }}</ref> When FSF released glibc 2.0 in January 1997, it had much more complete POSIX standards compliance, better internationalisation and multilingual function, ] capability, 64-bit data access, facilities for multithreaded applications, future version compatibility, and the code was more portable.<ref>{{cite web | url = http://people.redhat.com/~sopwith/old/glibc-vs-libc5.html | title = A Technical Comparison of glibc 2.x With Legacy System Libraries| author = Elliot Lee | year = 2001 |archiveurl = http://web.archive.org/web/20040411191201/http://people.redhat.com/~sopwith/old/glibc-vs-libc5.html |archivedate = 11 April 2004}}</ref> At this point, the Linux kernel developers discontinued their fork and returned to using FSF's glibc.<ref>{{cite web | url = http://www.linux.com/archive/feature/3874 | title = Forking: it could even happen to you | quote = the split between GNU LIBC and the Linux LIBC -- it went on for years while Linux stabilized, and then the forks re-merged into one project }}</ref>


The last used version of Linux libc used the internal name (]) <tt>libc.so.5</tt>. Following on from this, glibc 2.x on Linux uses the soname <tt>libc.so.6</tt><ref>{{cite web | url = http://linuxmafia.com/faq/Licensing_and_Law/forking.html | title = Fear of Forking essay, see "6. glibc --> Linux libc --> glibc" }}</ref> (] and ] architectures now use <tt>libc.so.6.1</tt>, instead). The soname is often abbreviated as libc6 (for example in the package name in ]) following the normal conventions for libraries. The last used version of Linux libc used the internal name (]) <tt>libc.so.5</tt>. Following on from this, glibc 2.x on Linux uses the soname <tt>libc.so.6</tt><ref>{{cite web | url = http://linuxmafia.com/faq/Licensing_and_Law/forking.html | title = Fear of Forking essay, see "6. glibc --> Linux libc --> glibc" }}</ref> (] and ] architectures now use <tt>libc.so.6.1</tt>, instead). The soname is often abbreviated as libc6 (for example in the package name in ]) following the normal conventions for libraries.
Line 38: Line 37:
According to ], 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.<ref>{{cite web | url = http://linuxmafia.com/faq/Licensing_and_Law/forking.html#foot25 | title = Fear of Forking, footnote on Stallman's merge comments }}</ref> According to ], 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.<ref>{{cite web | url = http://linuxmafia.com/faq/Licensing_and_Law/forking.html#foot25 | title = Fear of Forking, footnote on Stallman's merge comments }}</ref>


===Version history=== === Version history ===
<!---This version history uses dates from the ChangeLog files packaged in the 2.13 release.---> <!---This version history uses dates from the ChangeLog files packaged in the 2.13 release.--->
{| class="wikitable" {| class="wikitable"
Line 122: Line 121:


==Supported hardware and kernels== ==Supported hardware and kernels==
Glibc is used in systems that run many different ] and different ] architectures. Its most common use is in systems using the ] on ] hardware, however, officially supported hardware includes: ], ], ], ], ], ], and ]. It officially supports the ] and ] kernels. Additionally, there are heavily patched versions that run on the kernels of ] and ] (from which ] and ] systems are built, respectively), as well as the kernel of ].<ref>{{cite web|url=http://csclub.uwaterloo.ca/~dtbartle/opensolaris/|title=GNU/kOpenSolaris (GNU libc/base + OpenSolaris kernel)|last1=Bartley|first1=David|last2=Spang|first2=Michael|accessdate=2008-12-16}}</ref> It is also used (in an edited form) and named <tt>libroot.so</tt> in ] and ]. Glibc is used in systems that run many different ] and different ] architectures. Its most common use is in systems using the ] on ] hardware, however, officially supported hardware includes: ], ], ], ], ], ], and ]. It officially supports the ] and ] kernels. Additionally, there are heavily patched versions that run on the kernels of ] and ] (from which ] and ] systems are built, respectively), as well as the kernel of ].<ref>{{cite web|url=http://csclub.uwaterloo.ca/~dtbartle/opensolaris/|title=GNU/kOpenSolaris (GNU libc/base + OpenSolaris kernel)|last=Bartley|first=David|coauthors=Michael Spang|accessdate=2008-12-16}}</ref> It is also used (in an edited form) and named <tt>libroot.so</tt> in ] and ].


==Functionality== ==Functionality==
Line 130: Line 129:


==Use in small devices== ==Use in small devices==
glibc has been criticized as being "bloated" and slower than other libraries in the past, e.g. by ]<ref>{{cite web|last=Torvalds|first=Linus|url=http://ecos.sourceware.org/ml/libc-alpha/2002-01/msg00079.html|title=Posting to the glibc mailing list|date=9 January 2002 19:02:37}}</ref> and ] programmers. For this reason, several alternative C standard libraries have been created which emphasize a smaller footprint. Among them are ] (based mostly on ] and used in ]<ref>{{cite web|url=https://github.com/android/platform_bionic/tree/master/libc|title=Bionic libc README}}</ref>), ], ], ], ], ], and ] (used in ], ] and ]).<ref>{{cite web|url=http://www.eglibc.org|title=EGLIBC}}</ref> glibc has been criticized as being "bloated" and slower than other libraries in the past, e.g. by ]<ref>Linus Torvalds: , 9 January 2002 19:02:37</ref> and ] programmers. For this reason, several alternative C standard libraries have been created which emphasize a smaller footprint. Among them are ] (based mostly on ] and used in ]<ref></ref>), ], ], ], ], ], and ] (used in ], ] and ]).<ref></ref>


However, many small-device projects use GNU libc over the smaller alternatives because of its application support, standards compliance, and completeness. Examples include ]<ref>{{cite web However, many small-device projects use GNU libc over the smaller alternatives because of its application support, standards compliance, and completeness. Examples include ]<ref>{{cite web

Revision as of 02:12, 8 October 2013

"glibc" redirects here. Not to be confused with glib or gnulib.
GNU C Library
Original author(s)Roland McGrath
Developer(s)GNU Project
Initial release1987 (1987)
Repository
Operating systemUnix-like
TypeRuntime library
LicenseGNU Lesser General Public License
Websitewww.gnu.org/software/libc/

The GNU C Library, commonly known as glibc, is the GNU Project's implementation of the C standard library. Originally written by the Free Software Foundation (FSF) for the GNU operating system, the library's development had been overseen by a committee since 2001, with Ulrich Drepper as the lead contributor and maintainer. In March 2012, the steering committee voted to disband itself, in favor of a community-driven development process, with Ryan Arnold, Maxim Kuvyrkov, Joseph Myers, Carlos O'Donell, and Alexandre Oliva as non-decision making project stewards.

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

History

glibc 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. By 1992, it had the ANSI C-1989 and POSIX.1-1990 functions implemented and work was under way on POSIX.2.

A temporary fork

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. At this point, the Linux kernel developers discontinued their fork and returned to using FSF's glibc.

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 (Alpha and IA64 architectures now use libc.so.6.1, instead). The soname 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.

Version history

Version Date Notes Adoption
0.1 – 0.6 Oct 1991 – February 1992
1.0 February 1992
1.01 – 1.09.3 March 1992 – December 1994
1.90 – 1.102 May 1996 – January 1997
2.0 January 1997
2.0.1 January 1997
2.0.2 February 1997
2.0.91 December 1997
2.0.95 July 1998
2.1 February 1999
2.1.1 March 1999
2.2 November 2000
2.2.1 January 2001
2.2.2 February 2001
2.2.3 March 2001
2.2.4 July 2001
2.3 October 2002
2.3.1 October 2002
2.3.2 February 2003 Debian 3.1 (Sarge)
2.3.3 December 2003
2.3.4 December 2004 Standard for Linux Standard Base (LSB) 3.0, RHEL 4 (Update 5)
2.3.5 April 2005 SLES 9
2.3.6 November 2005 Debian 4.0 (Etch)
2.4 March 2006 Standard for LSB 4.0 SLES 10
2.5 September 2006 RHEL 5
2.6 May 2007
2.7 October 2007 Debian 5 (Lenny), Ubuntu 8.04
2.8 April 2008
2.9 November 2008
2.10 May 2009
2.11 October 2009 SLES 11, Ubuntu 10.04, eglibc used in Debian 6 (Squeeze)
2.12 May 2010 RHEL 6
2.13 January 2011 eglibc 2.13 used in Debian 7 (Wheezy)
2.14 June 2011
2.15 March 2012 Ubuntu 12.04 and 12.10
2.16 June 2012 x32 ABI support, ISO C11 compliance, SystemTap
2.17 December 2012 64-bit ARM support; Ubuntu 13.04
2.18 August 2013 Improved C++11 support. Support for Intel TSX lock elision. Support for the Xilinx MicroBlaze and IBM POWER8 microarchitectures.

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 includes: x86, Motorola 680x0, DEC Alpha, PowerPC, ETRAX CRIS, s390, and SPARC. 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 the kernel of OpenSolaris. It is also used (in an edited form) and named libroot.so in BeOS and Haiku.

Functionality

glibc provides the functionality required by the Single UNIX Specification, POSIX (1c, 1d, and 1j) and some of the functionality required by 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.

Use in small devices

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

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

See also

References

  1. A turning point for GNU libc, By Jonathan Corbet, 28 March 2012, LWN.net
  2. "glibc homepage". In 2001 The GNU C Library Steering Committee ..., was formed and currently consists of Mark Brown, Paul Eggert, Andreas Jaeger, Jakub Jelinek, Roland McGrath and Andreas Schwab.
  3. "Ulrich Drepper". LinkedIn. Retrieved 13 June 2012.
  4. Roland McGrath (26 March 2012). "glibc steering committee dissolving". Sourceware.org. Retrieved 13 June 2012.
  5. Joseph S. Myers (26 March 2012). "GNU C Library development and maintainers". Sourceware.org. Retrieved 13 June 2012.
  6. "http://www.gnu.org/bulletins/bull4.html". Most libraries are done. Roland McGrath has a nearly complete set of ANSI C library functions. We hope they will be ready some time this spring. {{cite web}}: External link in |title= (help)
  7. "GNU's Bulletin, vol. 1 no. 12". It now contains all of the ANSI C-1989 and POSIX.1-1990 functions, and work is in progress on POSIX.2 and Unix functions (BSD and System V)
  8. Elliot Lee (2001). "A Technical Comparison of glibc 2.x With Legacy System Libraries". Archived from the original on 11 April 2004.
  9. "Forking: it could even happen to you". the split between GNU LIBC and the Linux LIBC -- it went on for years while Linux stabilized, and then the forks re-merged into one project
  10. "Fear of Forking essay, see "6. glibc --> Linux libc --> glibc"".
  11. "Fear of Forking, footnote on Stallman's merge comments".
  12. Bartley, David. "GNU/kOpenSolaris (GNU libc/base + OpenSolaris kernel)". Retrieved 16 December 2008. {{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  13. Linus Torvalds: Posting to the glibc mailing list, 9 January 2002 19:02:37
  14. Bionic libc README
  15. EGLIBC
  16. "OpenMoko components". We will use glibc (not uClibC) ... The alternatives may save more space and be more optimized, but are more likely to give us integration headaches
  17. "Re: [Familiar] Which glibc for Familiar 0.8.4  ?". Question: which version of the GLIBC was used to build the Familiar 0.8.4 ? Answer: 2.3.3

External links

C programming language
Features
Standard library
Implementations
Compilers
IDEs
Comparison with
other languages
Descendant
languages
Designer
GNU Project
History
Licenses
Software
Contributors
Other topics
Categories:
Glibc: Difference between revisions Add topic