glibc

Glibc & The C library that all user applications will link to .

Glibc―所有用户应用程序都将链接到的C库。

This , of course , raises the question as to what facilities glibc provides .

这自然引出了glibc提供了哪些功能的问题。

UClibc is a reduced memory footprint replacement for glibc .

uClibc是glibc一个精简内存需求的替代品。

I failed to find any formalized C ( glibc ) function to find out free ( including reclaimable ) memory space .

我不能找到一个正式的C函数来找出自由（含可回收）内存的空间。

Your call ends up directed by glibc to a wrapper function with a name like__xstat () .

glibc将把该调用指向使用名称类似于xstat（）的包装器函数。

However , if you need the standard C library ( for your custom binaries ), there are other options beyond the massive glibc .

然而，如果我们需要标准的C库（我们自己定制的二进制可能需要这个库），除了巨大的glibc之外，我们还有其他选择。

A lot of glibc internals that make system calls make them directly inline rather than calling through to the standard " wrappers " .

许多发起系统调用的glibc内部特性都将系统调用直接实现为内联的，而不是通过标准的“包装器”进行调用。

While requiring fewer resources than glibc , porting applications to uClibc typically requires only a recompile .

尽管它需要的资源比glibc少，但是将应用程序移植到uClibc上通常只需要重新编译即可。

The glibc portal leads to the documentation and download location of the GNU / Linux and GNU / Hurd system library .

glibcportal提供了GNU/Linux和GNU/Hurd系统库的文档和下载位置。

The m17n C library parallels the basic text-processing functions of glibc ( and various other flavors of libc ) .

m17nC库可以类似地实现glibc（以及各种风格的libc）的一些基本的文本处理功能。

The standard BSD libc libraries and the glibc library underlying GNU / Linux and GNU / Hurd systems perform this function .

这项功能由GNU/Linux和GNU/Hurd系统下的标准BSDlibc库和glibc库完成。

In the case of the distribution I use , gentoo , you need to add " profile " to your USE flags and re-emerge glibc .

在我使用的发行版gentoo中，需要将“profile”添加到USE标志中，并重新执行emergeglibc。

Glibc V2.2 had not been released , and composite character input was based on fairly difficult standards coded in the more esoteric reaches of X.

当时GlibcV2.2还没有发布，复合字符输入基于一些完全不同的标准，这些标准是在更深奥的X级别上编码的。

Any programmer dealing with geographical data in any form or fashion is likely to encounter the base libraries in the same way any Linux systems programmer would encounter glibc .

以任何形式处理地理数据的所有编程人员都会遇到与Linux系统编程人员在glibc上遇到的相同的基础库问题。

The source code does not have external dependencies except for standard libraries like BDB , OpenSSL , TCL , STL , glibc and expat .

源代码除了像BDB，OpenSSL，TCL，STL，glibc和expat等等的标准库以外没有其它任何的外部依赖。

Most modern C standard libraries , like the libc library running the BSDs and the glibc running GNU / Linux systems , have the POSIX locale mechanism built in .

大多数当代C标准库，如运行在BDS上的libc库和运行在GNU/Linux系统上的glibc，都内建了POSIXlocale机制。

Build with the uClibc , which is a size-optimized C library that was developed for embedded systems , rather than building with the standard glibc ( GNU C library ) .

使用uClibc进行编译，这是一个对大小进行过优化的C库，它是为嵌入式系统开发的；而不要使用标准的glibc（GNUC库）来编译。

In this domain , a user-space application invoking the POSIX open call passes through the GNU C library ( glibc ) into the kernel and into system call de-multiplexing .

在这个域中，调用POSIXopen调用的用户空间应用程序经过GNUC库（glibc）进入内核和系统调用去多元化（de-multiplexing）。

The GNU glibc library has routines that work to counter this , but other libraries and any routines that walk the environment variable list can get into trouble in a hurry .

GNUglibc库对此有防范的例程，但是使用环境变量的其他库和任何例程可能很快陷入困境。

For distributions that do not ship with a libc_p as standard , you will need to check if it is installable separately , or you might need to download the glibc source and build it yourself .

对于没有按照标准提供libcp的发行版本来说，需要检查它是否可以单独安装，或者可能需要自己下载glibc的源代码并进行编译。

Every POSIX locale , regardless of whether it uses an ASCII single-byte or multibyte UTF-8 character encoding , relies on this character type , provided it is actually using a post-2.2 version of glibc .

每一种POSIXlocale，只要它实际上使用了post-2.2版本的glibc，不管它是使用ASCII单字节，还是使用多字节UTF-8字符编码，都要依赖于这种字符类型。