RHEL3 also includes a new and improved glibc, version 2.3.1.
RHEL3 中还包括一个新的改进的glibc，版本为 2.3.1。
Your call ends up directed by glibc to a wrapper function with a name like __xstat .
glibc将把该调用指向使用名称类似于__xstat的包装器函数。
This article USES OpenOffice.org version 1.0.1c, which matches the glibc version included with SLES 8.
本文所用的是OpenOffice.org版本1.0.1 c，它与SLES8所带的glibc版本相匹配。
This section will address changes in the GNU toolchain, referring to glibc, bintuils, as, ld, and gcc.
本节将介绍GNU工具链 中的变化，涉及到glibc、bintuils、as、ld和gcc。
Before you start using UTF-8 under Linux make sure the distribution has glibc 2.2 and XFree86 4.0 or newer versions.
在Linux平台上使用UTF - 8之前，请确信分发包里有glibc 2.2和XFree86 4.0或更新的版本。
However, if you need the standard C library (for your custom binaries), there are other options beyond the massive glibc.
然而，如果我们需要标准的C库（我们自己定制的二进制可能需要这个库），除了巨大的glibc 之外，我们还有其他选择。
However, the same source file compiled on a SLES9 system will not run on a SLES8 system because of the older level of glibc.
不过，在SLES9上编译的同样的源文件将因较老的glibc而不能在SLES8系统中运行。
However, the same source file compiled on a SLES10 system will not run on a SLES9 system because of the older level of glibc.
不过，在SLES10上编译的相同源代码将不能在SLES9系统上运行，因为它包含旧的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等等的标准库以外没有其它任何的外部依赖。
Required for the performance granted by NPTL threading, glibc 2.3.1 also brings more efficient libraries for Linux applications.
出于NPTL线程性能方面的需要，glibc2.3.1还为Linux应用程序引入了效率更高的库。
A lot of glibc internals that make system calls make them directly inline rather than calling through to the standard "wrappers".
许多发起系统调用的glibc内部特性都将系统调用直接实现为内联的，而不是通过标准的“包装器”进行调用。
Just using glibc-wide character string functions and POSIX locales, however, does not amount to a Linux internationalization architecture.
不过，只使用glibc - wide字符串功能和POSIXlocale，还不能构成Linux的国际化体系结构。
The glibc library supports locales and, as you have seen, uses the ISO standard 10646 to make UTF-8 display and editing functions possible.
glibc库支持locale，并且如您所看到的，可以使用ISO标准 10646来显示和编辑UTF-8。
The soon-to-be released SLES9 is currently in beta, as SUSE puts the finishing touches on a new GCC, glibc, and Linux 2.6 kernel combination.
即将发布的SLES9现在还在测试中，SUSE的最后一项任务是融合新的GCC、glibc和Linux 2.6内核。
The threading model in Linux has changed with the release of glibc 2.3 and the transition of the Linux kernel from version 2.4 to version 2.6.
随着glibc 2.3的发布和Linux内核从版本 2.4到版本 2.6的变迁，线程模型已经发生了变化。
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.
当时Glibc V2.2还没有发布，复合字符输入基于一些完全不同的标准，这些标准是在更深奥的x级别上编码的。
Specifically, SLES8 is based on a 2.4.21 kernel with a 2.2.5 version of glibc, while SLES9 is based on a 2.6 kernel with a 2.3 version of glibc.
具体地说，SLES8基于2.4.21内核，使用的是2.2.5版本的glibc，而SLES9基于2.6内核，使用的是2.3版本的glibc。
To get devfs up and running, you'll need to be using some version of Linux 2.4 (2.4.6 or 2.4.8 would be a good choice) and glibc 2.1.3 or greater.
要启动和运行devfs，需要使用Linux 2.4的一些版本(2.4.6或2.4.8就不错)以及glibc2.1.3或更高版本。
Officially, starting with GNU glibc 2.2, the type wchar_t is intended to be used only for 32-bit ISO 10646 values, independent of the currently used locale.
在正式情况下，从GNUglibc 2.2开始，wchar _ t类型只为32位的ISO 10646格式数值所特定使用，与当前使用的语言环境无关。
Eurotech: Eurotech provides embedded PC SBC and sponsors ET-Linux, a complete Linux system designed to run on small industrial computers and based on glibc 2.1.2.
Eurotech： Eurotech提供了嵌入式PCSBC并资助了ET - Linux，一个为在小型工业计算机上运行而专门设计的基于glibc 2.1.2的完全的Linux系统。
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库对此有防范的例程，但是使用环境变量的其他库和任何例程可能很快陷入困境。
NPTL implementation in the Linux kernel required the Linux kernel scheduler to be rewritten, the standard glibc to be extended, and updates to the GNU binutils to support it.
Linux内核中的 NPTL实现需要重写 Linux 内核调度程序（scheduler）、扩展标准的glibc以及更新GNUbinutils以支持该实现。
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上遇到的相同的基础库问题。
For example, if you take a closer look at the glibc libraries that are contained in the RHEL and SLES distributions, you see that RHEL4 contains version 2.3.4 and SLES9 is at 2.3.3.
例如，如果您仔细查看RHEL和SLES发行版中包含的glibc库，就会发现RHEL4包含的是版本2.3.4而SLES9包含的是2.3.3。
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.
对于没有按照标准提供 libc_p 的发行版本来说，需要检查它是否可以单独安装，或者可能需要自己下载glibc 的源代码并进行编译。
For example, a binary that was compiled on a SLES8 system with a version of glibc at 2.2.5 will also run on a SLES9 system with a glibc version at 2.3 since the 2.3 version is backward compatible.
例如，在SLES8系统中使用glibc版本2.2.5编译的二进制代码，将可以在SLES9系统中使用glibc版本2.3运行，因为2.3版本是向后兼容的。
For example, a binary that was compiled on a SLES9 system with a version of glibc at 2.3.3 will also run on a SLES10 system with a glibc version at 2.4 since the 2.4 version is backward compatible.
例如，在包含glibc 2.3.3的SLES9系统上编译的二进制文件可以在包含glibc 2.4的SLES10系统上运行，因为2.4版本是向后兼容的。
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字符编码，都要依赖于这种字符类型。
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字符编码，都要依赖于这种字符类型。
应用推荐