在操作的时候犯了大错，不想多说，一句话：系统无法正常登录了……之前还不清楚libc或glibc在Linux系统上的重要性（现在真的是切切实实的认识到了，沉痛的经验教训啊！）

搜索关键字：

• linux libc.so.
• linux libc.so.6 stackoverflow.com
• site:stackoverflow.com LD_LIBRARY_PATH LD_PRELOAD

==

env
export LD_LIBRARY_PATH=/lib/i386-linux-gnu
export LD_PRELOAD=/lib/i386-linux-gnu/libc-2.19.so

libc implements both standard C functions like strcpy() and POSIX functions (which may be system calls) like getpid(). Note that not all standard C functions are in libc – most math functions are in libm.

You cannot directly make system calls in the same way that you call normal functions because calls to the kernel aren’t normal function calls, so they can’t be resolved by the linker. Instead, architecture-specific assembly language thunks are used to call into the kernel – you can of course write these directly in your own program too, but you don’t need to because libc provides them for you.

Note that in Linux it is the combination of the kernel and libc that provides the POSIX API. libc adds a decent amount of value – not every POSIX function is necessarily a system call, and for the ones that are, the kernel behaviour isn’t always POSIX conforming.

libc is a single library file (both .so and .a versions are available) and in most cases resides in /usr/lib. However, the glibc (GNU libc) project provides more than just libc – it also provides the libm mentioned earlier, and other core libraries like libpthread. So libc is just one of the libraries provided by glibc – and there are other alternate implementations of libc other than glibc.

=

Why glibc binary is called libc.so.6 not a libc.so.1 or libc.so.4?

Those SONAMEs have already been used. Since the new version of the library presents a break in the interface, a new major SONAME number must be used for it.

=

The term “libc” is commonly used as a shorthand for the “standard C library“, a library of standard functions that can be used by all C programs (and sometimes by programs in other languages).  Because of some history (see below), use of the term “libc” to refer to the standard C library is somewhat ambiguous on Linux.

glibc

By far the most widely used C library on Linux is the GNU C Library <http://www.gnu.org/software/libc/>, often referred to as glibc.

This is the C library that is nowadays used in all major Linux distributions.  It is also the C library whose details are documented in the relevant pages of the man-pages project (primarily in Section 3 of the manual).  Documentation of glibc is also available in the glibc manual, available via the command info libc.  Release 1.0 of glibc was made in September 1992.  (There were earlier 0.x releases.)

The next major release of glibc was 2.0, at the beginning of 1997.

The pathname /lib/libc.so.6 (or something similar) is normally a symbolic link that points to the location of the glibc library, and executing this pathname will cause glibc to display various information about the version installed on your system.

Linux libc

In the early to mid 1990s, there was for a while Linux libc, a fork of glibc 1.x created by Linux developers who felt that glibc development at the time was not sufficing for the needs of Linux.  Often, this library was referred to (ambiguously) as just “libc”.  Linux libc released major versions 2, 3, 4, and 5 (as well as many minor versions of those releases).  For a while, Linux libc was the standard C library in many Linux distributions.

However, notwithstanding the original motivations of the Linux libc effort, by the time glibc 2.0 was released (in 1997), it was clearly superior to Linux libc, and all major Linux distributions that had been using Linux libc soon switched back to glibc.  Since this switch occurred long ago, man-pages no longer takes care to document Linux libc details.  Nevertheless, the history is visible in vestiges of information about Linux libc that remain in some manual pages, in particular, references to libc4 and libc5.

Other C libraries

There are various other less widely used C libraries for Linux.

These libraries are generally smaller than glibc, both in terms of features and memory footprint, and often intended for building small binaries, perhaps targeted at development for embedded Linux systems.

Among such libraries are uClibc <http://www.uclibc.org/>, dietlibc <http://www.fefe.de/dietlibc/>, and musl libc <http://www.musl-libc.org/>.  Details of these libraries are covered by the man-pages project, where they are known.

==

参考链接：

• http://man7.org/linux/man-pages/man7/libc.7.html
• http://stackoverflow.com/questions/11372872/what-the-role-of-libcglibc-in-our-linux-app
• =
• http://en.wikipedia.org/wiki/GNU_C_Library
• https://sourceware.org/glibc/wiki/FAQ
• http://www.gnu.org/software/libc/
• =
• http://stackoverflow.com/questions/6495817/why-glibc-binary-is-called-libc-so-6-not-a-libc-so-1-or-libc-so-4
• http://stackoverflow.com/questions/12249547/how-to-recover-after-deleting-the-symbolic-link-libc-so-6
• http://stackoverflow.com/questions/19682782/relevance-of-libc-so-6-in-linux-kernel
• https://blogs.oracle.com/ksplice/entry/hello_from_a_libc_free
• =
• http://stackoverflow.com/questions/14715175/what-is-the-difference-between-ld-preload-path-and-ld-library-path
• http://joxeankoret.com/blog/2012/11/14/patching-old-linux-binaries-to-work-with-recent-libc-versions/
• =
• http://stackoverflow.com/questions/3436008/how-to-determine-version-of-glibc-glibcxx-binary-will-depend-on
• http://stackoverflow.com/questions/2856438/how-can-i-link-to-a-specific-glibc-version
• http://stackoverflow.com/questions/725472/static-link-of-shared-library-function-in-gcc
• =
• http://www.tldp.org/HOWTO/Glibc2-HOWTO-5.html
• http://www.tldp.org/FAQ/Linux-FAQ/system-libraries.html
• =
• http://www.linuxfromscratch.org/lfs/view/development/chapter06/glibc.html