glibc, die GNU C-Bibliothek, ist eine freie Implementierung der C-Standard-Bibliothek, die vom GNU-Projekt zusammen mit der GNU Compiler Collection entwickelt wird.

Die glibc steht unter der LGPL, was den Einsatz der Bibliothek bei nicht freier Software ermöglicht. Die glibc-Bibliothek gehört zu den fundamentalsten und wichtigsten Bibliotheken von unixoiden Betriebssystemen.

Eigenschaften

Eines der Designziele der glibc ist Portabilität über verschiedene Softwareplattformen, daher ist sie auch für eine Reihe von Betriebssystemen verfügbar. Einige Betriebssysteme, darunter GNU/Linux, benutzen die glibc als ihre offizielle Standard-C-Bibliothek. Die Bibliotheken der glibc sind selbst zum größten Teil auch in C geschrieben, laufzeitkritische Routinen verwenden jedoch Assembler-Code.

Geschichte

Siehe auch

• diet libc
• musl
• Newlib
• uClibc

Literatur

• Sandra Loosemore et al.: The GNU C Library: Application Fundamentals (for GNU C Libraries Version 2.3.x) (PDF; 2,6 MB). GNU Press, Boston, 2004. ISBN 978-1-8821142-2-1.

Weblinks

• Offizielle Website des GNU-Projekts zur glibc (engl.)
• The GNU C Library Reference Manual (engl.)
• Das glibc-Wiki
• Comparison of C/POSIX standard library implementations for Linux (engl.) – glibc 2.19 im Vergleich zu kompakten Alternativen

Einzelnachweise

1. ↑ Andreas K. Huettel: The GNU C Library version 2.38 is now available. 31. Juli 2023 (englisch, abgerufen am 1. August 2023).
2. ↑ Bug 5070 - glibc-2.5: ../sysdeps/unix/sysv/linux/check_pf.c:68: make_request: Assertion fails
3. 1 2 Ulrich Drepper: Dictatorship of the Minorities. udrepper.livejournal.com, 25. Mai 2005, abgerufen am 15. Januar 2012 (englisch): „Which architectures are worthwhile supporting? [...]. Not only do we have to look for irrelevance (what percentage cares about Vax, PArisc) support, we also have to look at the level of added complexity the support requires. Some ABIs are just deliberately defined to be different from others (see IA-64) which requires huge amounts of effort to be spent. There are also significantly diverging capabilities (e. g., the lack of atomic operations in too many architectures). This far too often causes to unnecessarily crippled code since writing code in a way which allows optimal use in all situations is very difficult. The solution must be to restrict support to only a handful of architectures which are supported in the project. All other support must happen outside the tree and therefore all the work has to be done by the special interest groups. I don't want to say we follow all these points perfectly, but for a big project glibc certainly comes closest to this.“ 
4. ↑ Linus Torvalds: Posting to the glibc mailing list, 9. Januar 2002 19:02:37
5. ↑ Jonathan Corbet: A turning point for GNU libc. LWN.net, 28. März 2012; abgerufen im 1. Januar 1: „Of the nearly 19,000 commits found in the project's git repository (which contains changes back to 1995), over 12,000 were made by Ulrich.“ 
6. ↑ glibc homepage. Abgerufen im 1. Januar 1: „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.“ 
7. ↑ Ulrich Drepper: RMS is at it again. sourceware.org, 26. Juni 2000, abgerufen am 20. November 2015: „A few weeks ago RMS started the next attack on me (a single mail, followed by indirect tries to take influence, followed by another mail today). The essence is that he complains I am not following "GNU policies" and therefore have to be replaced by a steering committee of which I could be a part. Some of you (namely Roland and Andreas S.) probably knowabout this since he proposed both as other members of the committee. In addition there was Mark Brown listed (I know somebody of this name at IBM who would also fit in this group but I'm not sure whether it is really him.) Anyhow, I completely reject this. It is not helping at all, the opposite is true. First, I am not aware of any essential policies I'm violating. The only ones are that I'm not following orders from RMS which clearly have political intends (which is of course a sacrilege) and possibly that I do not care about Winblowz (if the latter counts at all). None of this will change in any way.“ 
8. ↑ Ulrich Drepper: glibc 2.2.4. sourceware.com, 15. August 2001, abgerufen am 29. November 2015: „And now for some not so nice things. Stallman recently tried what I would call a hostile takeover of the glibc development. He tried to conspire behind my back and persuade the other main developers to take control so that in the end he is in control and can dictate whatever pleases him. This attempt failed but he kept on pressuring people everywhere and it got really ugly. In the end I agreed to the creation of a so-called "steering committee" (SC).“ 
9. ↑ rms-accused-of-attempting-glibc-hostile-takeover auf slashdot.com am 19. August 2001
10. ↑ Sourceware-Information zum glibc-Repo
11. ↑ http://www.eglibc.org/home
12. ↑ http://www.eglibc.org/faq
13. ↑ Aurélien Jarno: Debian is switching to EGLIBC. aurel32.net, 5. Mai 2009, abgerufen am 15. Januar 2012 (englisch): „More friendly upstream (especially with regard to embedded architectures): “Encourage cooperation, communication, civility, and respect among developers” (as opposed to this).“ 
14. ↑ timothy: Debian Switching From Glibc To Eglibc. Slashdot, 6. Mai 2009, abgerufen am 14. Januar 2012 (englisch). 
15. ↑ Debian is switching (back) to GLIBC. Aurélien, 19. Juni 2014, abgerufen am 19. Juni 2014 (englisch). 
16. ↑ http://www.eglibc.org/news
17. ↑ http://ftp.gnu.org/gnu/glibc/
18. ↑ Andreas Jaeger: Large File Support in Linux. SUSE GmbH, 15. Februar 2015; abgerufen im 1. Januar 1.