[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Commits] r17336 - in /fsf/trunk/libc: ./ include/ manual/ posix/ stdlib/ sysdeps/gnu/ sysdeps/sparc/sparc32/fpu/ sysdeps/sparc/sparc3...
- To: commits@xxxxxxxxxx
- Subject: [Commits] r17336 - in /fsf/trunk/libc: ./ include/ manual/ posix/ stdlib/ sysdeps/gnu/ sysdeps/sparc/sparc32/fpu/ sysdeps/sparc/sparc3...
- From: eglibc@xxxxxxxxxx
- Date: Wed, 29 Feb 2012 00:02:43 -0000
Author: eglibc
Date: Wed Feb 29 00:02:39 2012
New Revision: 17336
Log:
Import glibc-mainline for 2012-02-29
Added:
fsf/trunk/libc/manual/macros.texi
fsf/trunk/libc/posix/bug-regex33.c
fsf/trunk/libc/sysdeps/sparc/sparc32/fpu/s_copysign.S
fsf/trunk/libc/sysdeps/sparc/sparc32/fpu/s_copysignf.S
fsf/trunk/libc/sysdeps/sparc/sparc32/sparcv9/fpu/s_floor.S
fsf/trunk/libc/sysdeps/sparc/sparc32/sparcv9/fpu/s_floorf.S
fsf/trunk/libc/sysdeps/sparc/sparc64/fpu/s_copysign.S
fsf/trunk/libc/sysdeps/sparc/sparc64/fpu/s_copysignf.S
fsf/trunk/libc/sysdeps/sparc/sparc64/fpu/s_floor.S
fsf/trunk/libc/sysdeps/sparc/sparc64/fpu/s_floorf.S
Modified:
fsf/trunk/libc/ChangeLog
fsf/trunk/libc/INSTALL
fsf/trunk/libc/Makefile
fsf/trunk/libc/NEWS
fsf/trunk/libc/NOTES
fsf/trunk/libc/include/dirent.h
fsf/trunk/libc/manual/arith.texi
fsf/trunk/libc/manual/charset.texi
fsf/trunk/libc/manual/conf.texi
fsf/trunk/libc/manual/contrib.texi
fsf/trunk/libc/manual/creature.texi
fsf/trunk/libc/manual/crypt.texi
fsf/trunk/libc/manual/ctype.texi
fsf/trunk/libc/manual/errno.texi
fsf/trunk/libc/manual/filesys.texi
fsf/trunk/libc/manual/header.texi
fsf/trunk/libc/manual/install.texi
fsf/trunk/libc/manual/intro.texi
fsf/trunk/libc/manual/io.texi
fsf/trunk/libc/manual/job.texi
fsf/trunk/libc/manual/lang.texi
fsf/trunk/libc/manual/libc.texinfo
fsf/trunk/libc/manual/llio.texi
fsf/trunk/libc/manual/locale.texi
fsf/trunk/libc/manual/maint.texi
fsf/trunk/libc/manual/math.texi
fsf/trunk/libc/manual/memory.texi
fsf/trunk/libc/manual/message.texi
fsf/trunk/libc/manual/nss.texi
fsf/trunk/libc/manual/pattern.texi
fsf/trunk/libc/manual/process.texi
fsf/trunk/libc/manual/resource.texi
fsf/trunk/libc/manual/search.texi
fsf/trunk/libc/manual/setjmp.texi
fsf/trunk/libc/manual/signal.texi
fsf/trunk/libc/manual/socket.texi
fsf/trunk/libc/manual/startup.texi
fsf/trunk/libc/manual/stdio.texi
fsf/trunk/libc/manual/string.texi
fsf/trunk/libc/manual/sysinfo.texi
fsf/trunk/libc/manual/syslog.texi
fsf/trunk/libc/manual/terminal.texi
fsf/trunk/libc/manual/time.texi
fsf/trunk/libc/manual/users.texi
fsf/trunk/libc/posix/Makefile
fsf/trunk/libc/posix/regex_internal.c
fsf/trunk/libc/stdlib/fmtmsg.c
fsf/trunk/libc/sysdeps/gnu/errlist.c
fsf/trunk/libc/sysdeps/sparc/sparc32/sparcv9/fpu/s_ceil.S
fsf/trunk/libc/sysdeps/sparc/sparc32/sparcv9/fpu/s_ceilf.S
fsf/trunk/libc/sysdeps/sparc/sparc64/fpu/s_ceil.S
fsf/trunk/libc/sysdeps/sparc/sparc64/fpu/s_ceilf.S
Modified: fsf/trunk/libc/ChangeLog
==============================================================================
--- fsf/trunk/libc/ChangeLog (original)
+++ fsf/trunk/libc/ChangeLog Wed Feb 29 00:02:39 2012
@@ -1,3 +1,92 @@
+2012-02-28 Stanislav Brabec <sbrabec@xxxxxxx>
+
+ [BZ #13637]
+ * posix/regex_internal.c (re_string_skip_chars): Fix miscomputation
+ of remain_len that may cause incomplete multi-byte character and
+ false match.
+ * posix/bug-regex33.c: New file.
+ * posix/Makefile (tests): Add bug-regex33.
+
+2012-02-28 Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
+
+ * manual/macros.texi: New file.
+ * Makefile (INSTALL, NOTES): Depend on manual/macros.texi.
+ * manual/libc.texinfo: Include macros.texi.
+ * manual/creatute.texi: Likewise.
+ * manual/install.texi: Likewise.
+ * manual/arith.texi: Use macros @Theglibc{}, @theglibc{} and
+ @glibcadj{} in references to the GNU C Library.
+ * manual/charset.texi: Likewise.
+ * manual/conf.texi: Likewise.
+ * manual/contrib.texi: Likewise. Consistently use "GNU C Library"
+ when not using those macros.
+ * manual/creature.texi: Likewise.
+ * manual/crypt.texi: Likewise.
+ * manual/errno.texi: Likewise.
+ * manual/filesys.texi: Likewise.
+ * manual/header.texi: Likewise.
+ * manual/install.texi: Likewise.
+ * manual/intro.texi: Likewise.
+ * manual/io.texi: Likewise.
+ * manual/job.texi: Likewise.
+ * manual/lang.texi: Likewise.
+ * manual/libc.texiinfo: Likewise.
+ * manual/llio.texi: Likewise.
+ * manual/locale.texi: Likewise.
+ * manual/maint.texi: Likewise.
+ * manual/math.texi: Likewise.
+ * manual/memory.texi: Likewise.
+ * manual/message.texi: Likewise.
+ * manual/nss.texi: Likewise.
+ * manual/pattern.texi: Likewise.
+ * manual/process.texi: Likewise.
+ * manual/resource.texi: Likewise.
+ * manual/search.texi: Likewise.
+ * manual/setjmp.texi: Likewise.
+ * manual/signal.texi: Likewise.
+ * manual/socket.texi: Likewise.
+ * manual/startup.texi: Likewise.
+ * manual/stdio.texi: Likewise.
+ * manual/string.texi: Likewise.
+ * manual/sysinfo.texi: Likewise.
+ * manual/syslog.texi: Likewise.
+ * manual/terminal.texi: Likewise.
+ * manual/time.texi: Likewise.
+ * manual/users.texi: Likewise.
+ * INSTALL: Regenerated.
+ * NOTES: Regenerated.
+ * sysdeps/gnu/errlist.c: Regenerated.
+
+2012-02-28 Andreas Schwab <schwab@xxxxxxxxxxxxxx>
+
+ * include/dirent.h: Include <dirstream.h> before
+ <dirent/dirent.h>.
+
+2012-02-28 David S. Miller <davem@xxxxxxxxxxxxx>
+
+ * sysdeps/sparc/sparc32/fpu/s_copysign.S: New file.
+ * sysdeps/sparc/sparc32/fpu/s_copysignf.S: New file.
+ * sysdeps/sparc/sparc64/fpu/s_copysign.S: New file.
+ * sysdeps/sparc/sparc64/fpu/s_copysignf.S: New file.
+
+2012-02-27 David S. Miller <davem@xxxxxxxxxxxxx>
+
+ * sysdeps/sparc/sparc32/sparcv9/fpu/s_floor.S: New file.
+ * sysdeps/sparc/sparc32/sparcv9/fpu/s_floorf.S: New file.
+ * sysdeps/sparc/sparc64/fpu/s_floor.S: New file.
+ * sysdeps/sparc/sparc64/fpu/s_floorf.S: New file.
+
+ * sysdeps/sparc/sparc32/sparcv9/fpu/s_ceil.S: Fix accidental use of
+ frame pointer instead of stack pointer relative arg slot.
+ * sysdeps/sparc/sparc32/sparcv9/fpu/s_ceilf.S: Likewise.
+ * sysdeps/sparc/sparc64/fpu/s_ceil.S: Likewise.
+ * sysdeps/sparc/sparc64/fpu/s_ceilf.S: Likewise.
+
+2012-02-27 Carlos O'Donell <carlos_odonell@xxxxxxxxxx>
+
+ [BZ #3992]
+ * stdlib/fmtmsg.c: Use of uint32_t requires stdint.h.
+
2012-02-27 David S. Miller <davem@xxxxxxxxxxxxx>
* sysdeps/sparc/sparc32/sparcv9/fpu/s_ceil.S: Fix comment formatting.
Modified: fsf/trunk/libc/INSTALL
==============================================================================
--- fsf/trunk/libc/INSTALL (original)
+++ fsf/trunk/libc/INSTALL Wed Feb 29 00:02:39 2012
@@ -6,24 +6,24 @@
and describes problems you may experience with compilation and
installation. It is updated more frequently than this manual.
- Features can be added to GNU Libc via "add-on" bundles. These are
-separate tar files, which you unpack into the top level of the source
-tree. Then you give `configure' the `--enable-add-ons' option to
-activate them, and they will be compiled into the library.
+ Features can be added to the GNU C Library via "add-on" bundles.
+These are separate tar files, which you unpack into the top level of
+the source tree. Then you give `configure' the `--enable-add-ons'
+option to activate them, and they will be compiled into the library.
You will need recent versions of several GNU tools: definitely GCC
and GNU Make, and possibly others. *Note Tools for Compilation::,
below.
-Configuring and compiling GNU Libc
-==================================
-
-GNU libc cannot be compiled in the source directory. You must build it
-in a separate build directory. For example, if you have unpacked the
-glibc sources in `/src/gnu/glibc-VERSION', create a directory
-`/src/gnu/glibc-build' to put the object files in. This allows
-removing the whole build directory in case an error occurs, which is
-the safest way to get a fresh start and should always be done.
+Configuring and compiling the GNU C Library
+===========================================
+
+The GNU C Library cannot be compiled in the source directory. You must
+build it in a separate build directory. For example, if you have
+unpacked the GNU C Library sources in `/src/gnu/glibc-VERSION', create
+a directory `/src/gnu/glibc-build' to put the object files in. This
+allows removing the whole build directory in case an error occurs,
+which is the safest way to get a fresh start and should always be done.
From your object directory, run the shell script `configure' located
at the top level of the source tree. In the scenario above, you'd type
@@ -36,10 +36,10 @@
`configure' takes many options, but the only one that is usually
mandatory is `--prefix'. This option tells `configure' where you want
-glibc installed. This defaults to `/usr/local', but the normal setting
-to install as the standard system library is `--prefix=/usr' for
-GNU/Linux systems and `--prefix=' (an empty prefix) for GNU/Hurd
-systems.
+the GNU C Library installed. This defaults to `/usr/local', but the
+normal setting to install as the standard system library is
+`--prefix=/usr' for GNU/Linux systems and `--prefix=' (an empty prefix)
+for GNU/Hurd systems.
It may also be useful to set the CC and CFLAGS variables in the
environment when running `configure'. CC selects the C compiler that
@@ -59,16 +59,16 @@
`--with-headers=DIRECTORY'
Look for kernel header files in DIRECTORY, not `/usr/include'.
- Glibc needs information from the kernel's header files describing
- the interface to the kernel. Glibc will normally look in
- `/usr/include' for them, but if you specify this option, it will
- look in DIRECTORY instead.
+ The GNU C Library needs information from the kernel's header files
+ describing the interface to the kernel. The GNU C Library will
+ normally look in `/usr/include' for them, but if you specify this
+ option, it will look in DIRECTORY instead.
This option is primarily of use on a system where the headers in
- `/usr/include' come from an older version of glibc. Conflicts can
- occasionally happen in this case. You can also use this option if
- you want to compile glibc with a newer set of kernel headers than
- the ones found in `/usr/include'.
+ `/usr/include' come from an older version of the GNU C Library.
+ Conflicts can occasionally happen in this case. You can also use
+ this option if you want to compile the GNU C Library with a newer
+ set of kernel headers than the ones found in `/usr/include'.
`--enable-add-ons[=LIST]'
Specify add-on packages to include in the build. If this option is
@@ -93,7 +93,7 @@
Use the binutils (assembler and linker) in `DIRECTORY', not the
ones the C compiler would default to. You can use this option if
the default binutils on your system cannot deal with all the
- constructs in the GNU C library. In that case, `configure' will
+ constructs in the GNU C Library. In that case, `configure' will
detect the problem and suppress these constructs, so that the
library will still be usable, but functionality may be lost--for
example, you can't build a shared libc with old binutils.
@@ -132,10 +132,10 @@
`--host=HOST-SYSTEM'
These options are for cross-compiling. If you specify both
options and BUILD-SYSTEM is different from HOST-SYSTEM, `configure'
- will prepare to cross-compile glibc from BUILD-SYSTEM to be used
- on HOST-SYSTEM. You'll probably need the `--with-headers' option
- too, and you may have to override CONFIGURE's selection of the
- compiler and/or binutils.
+ will prepare to cross-compile the GNU C Library from BUILD-SYSTEM
+ to be used on HOST-SYSTEM. You'll probably need the
+ `--with-headers' option too, and you may have to override
+ CONFIGURE's selection of the compiler and/or binutils.
If you only specify `--host', `configure' will prepare for a
native compile but use what you specify instead of guessing what
@@ -167,8 +167,8 @@
do not use the built library, and report a bug after verifying that the
problem is not already known. *Note Reporting Bugs::, for instructions
on reporting bugs. Note that some of the tests assume they are not
-being run by `root'. We recommend you compile and test glibc as an
-unprivileged user.
+being run by `root'. We recommend you compile and test the GNU C
+Library as an unprivileged user.
Before reporting bugs make sure there is no problem with your system.
The tests (and later installation) use some pre-existing files of the
@@ -188,7 +188,7 @@
file is included and parsed by `make' and has to follow the conventions
for makefiles.
- It is easy to configure the GNU C library for cross-compilation by
+ It is easy to configure the GNU C Library for cross-compilation by
setting a few variables in `configparms'. Set `CC' to the
cross-compiler for the target you configured the library for; it is
important to use this same `CC' value when running `configure', like
@@ -204,16 +204,16 @@
To install the library and its header files, and the Info files of the
manual, type `env LANGUAGE=C LC_ALL=C make install'. This will build
things, if necessary, before installing them; however, you should still
-compile everything first. If you are installing glibc as your primary
-C library, we recommend that you shut the system down to single-user
-mode first, and reboot afterward. This minimizes the risk of breaking
-things when the library changes out from underneath.
+compile everything first. If you are installing the GNU C Library as
+your primary C library, we recommend that you shut the system down to
+single-user mode first, and reboot afterward. This minimizes the risk
+of breaking things when the library changes out from underneath.
`make install' will do the entire job of upgrading from a previous
-installation of glibc 2.x. There may sometimes be headers left behind
-from the previous installation, but those are generally harmless. If
-you want to avoid leaving headers behind you can do things in the
-following order.
+installation of the GNU C Library version 2.x. There may sometimes be
+headers left behind from the previous installation, but those are
+generally harmless. If you want to avoid leaving headers behind you
+can do things in the following order.
You must first build the library (`make'), optionally check it
(`make check'), switch the include directories and then install (`make
@@ -224,19 +224,20 @@
library. The new `/usr/include', after switching the include
directories and before installing the library should contain the Linux
headers, but nothing else. If you do this, you will need to restore
-any headers from non-glibc libraries youself after installing the
-library.
-
- You can install glibc somewhere other than where you configured it
-to go by setting the `install_root' variable on the command line for
-`make install'. The value of this variable is prepended to all the
-paths for installation. This is useful when setting up a chroot
-environment or preparing a binary distribution. The directory should be
-specified with an absolute file name.
-
- Glibc includes a daemon called `nscd', which you may or may not want
-to run. `nscd' caches name service lookups; it can dramatically
-improve performance with NIS+, and may help with DNS as well.
+any headers from libraries other than the GNU C Library yourself after
+installing the library.
+
+ You can install the GNU C Library somewhere other than where you
+configured it to go by setting the `install_root' variable on the
+command line for `make install'. The value of this variable is
+prepended to all the paths for installation. This is useful when
+setting up a chroot environment or preparing a binary distribution.
+The directory should be specified with an absolute file name.
+
+ The GNU C Library includes a daemon called `nscd', which you may or
+may not want to run. `nscd' caches name service lookups; it can
+dramatically improve performance with NIS+, and may help with DNS as
+well.
One auxiliary program, `/usr/libexec/pt_chown', is installed setuid
`root'. This program is invoked by the `grantpt' function; it sets the
@@ -249,12 +250,12 @@
`login/programs/pt_chown.c'.
After installation you might want to configure the timezone and
-locale installation of your system. The GNU C library comes with a
+locale installation of your system. The GNU C Library comes with a
locale database which gets configured with `localedef'. For example, to
set up a German locale with name `de_DE', simply issue the command
`localedef -i de_DE -f ISO-8859-1 de_DE'. To configure all locales
-that are supported by glibc, you can issue from your build directory the
-command `make localedata/install-locales'.
+that are supported by the GNU C Library, you can issue from your build
+directory the command `make localedata/install-locales'.
To configure the locally used timezone, set the `TZ' environment
variable. The script `tzselect' helps you to select the right value.
@@ -269,7 +270,7 @@
=================================
We recommend installing the following GNU tools before attempting to
-build the GNU C library:
+build the GNU C Library:
* GNU `make' 3.79 or newer
@@ -282,17 +283,17 @@
* GCC 4.3 or newer, GCC 4.6 recommended
GCC 4.3 or higher is required; as of this writing, GCC 4.6 is the
- compiler we advise to use to build the GNU C library.
-
- You can use whatever compiler you like to compile programs that
- use GNU libc.
+ compiler we advise to use to build the GNU C Library.
+
+ You can use whatever compiler you like to compile programs that use
+ the GNU C Library.
Check the FAQ for any special compiler issues on particular
platforms.
* GNU `binutils' 2.15 or later
- You must use GNU `binutils' (as and ld) to build the GNU C library.
+ You must use GNU `binutils' (as and ld) to build the GNU C Library.
No other assembler or linker has the necessary functionality at the
moment.
@@ -338,41 +339,42 @@
Specific advice for GNU/Linux systems
=====================================
-If you are installing GNU libc on a GNU/Linux system, you need to have
-the header files from a 2.6.19.1 or newer kernel around for reference.
-These headers must be installed using `make headers_install'; the
-headers present in the kernel source directory are not suitable for
-direct use by GNU libc. You do not need to use that kernel, just have
-its headers installed where glibc can access them, referred to here as
-INSTALL-DIRECTORY. The easiest way to do this is to unpack it in a
-directory such as `/usr/src/linux-VERSION'. In that directory, run
-`make headers_install INSTALL_HDR_PATH=INSTALL-DIRECTORY'. Finally,
-configure glibc with the option
-`--with-headers=INSTALL-DIRECTORY/include'. Use the most recent kernel
-you can get your hands on. (If you are cross-compiling GNU libc, you
-need to specify `ARCH=ARCHITECTURE' in the `make headers_install'
-command, where ARCHITECTURE is the architecture name used by the Linux
-kernel, such as `x86' or `powerpc'.)
-
- After installing GNU libc, you may need to remove or rename
+If you are installing the GNU C Library on a GNU/Linux system, you need
+to have the header files from a 2.6.19.1 or newer kernel around for
+reference. These headers must be installed using `make
+headers_install'; the headers present in the kernel source directory
+are not suitable for direct use by the GNU C Library. You do not need
+to use that kernel, just have its headers installed where the GNU C
+Library can access them, referred to here as INSTALL-DIRECTORY. The
+easiest way to do this is to unpack it in a directory such as
+`/usr/src/linux-VERSION'. In that directory, run `make headers_install
+INSTALL_HDR_PATH=INSTALL-DIRECTORY'. Finally, configure the GNU C
+Library with the option `--with-headers=INSTALL-DIRECTORY/include'.
+Use the most recent kernel you can get your hands on. (If you are
+cross-compiling the GNU C Library, you need to specify
+`ARCH=ARCHITECTURE' in the `make headers_install' command, where
+ARCHITECTURE is the architecture name used by the Linux kernel, such as
+`x86' or `powerpc'.)
+
+ After installing the GNU C Library, you may need to remove or rename
directories such as `/usr/include/linux' and `/usr/include/asm', and
replace them with copies of directories such as `linux' and `asm' from
`INSTALL-DIRECTORY/include'. All directories present in
-`INSTALL-DIRECTORY/include' should be copied, except that GNU libc
-provides its own version of `/usr/include/scsi'; the files provided by
-the kernel should be copied without replacing those provided by GNU
-libc. The `linux', `asm' and `asm-generic' directories are required to
-compile programs using GNU libc; the other directories describe
-interfaces to the kernel but are not required if not compiling programs
-using those interfaces. You do not need to copy kernel headers if you
-did not specify an alternate kernel header source using
-`--with-headers'.
-
- GNU/Linux expects some components of the libc installation to be in
-`/lib' and some in `/usr/lib'. This is handled automatically if you
-configure glibc with `--prefix=/usr'. If you set some other prefix or
-allow it to default to `/usr/local', then all the components are
-installed there.
+`INSTALL-DIRECTORY/include' should be copied, except that the GNU C
+Library provides its own version of `/usr/include/scsi'; the files
+provided by the kernel should be copied without replacing those
+provided by the GNU C Library. The `linux', `asm' and `asm-generic'
+directories are required to compile programs using the GNU C Library;
+the other directories describe interfaces to the kernel but are not
+required if not compiling programs using those interfaces. You do not
+need to copy kernel headers if you did not specify an alternate kernel
+header source using `--with-headers'.
+
+ GNU/Linux expects some components of the GNU C Library installation
+to be in `/lib' and some in `/usr/lib'. This is handled automatically
+if you configure the GNU C Library with `--prefix=/usr'. If you set
+some other prefix or allow it to default to `/usr/local', then all the
+components are installed there.
You cannot use `nscd' with 2.0 kernels, due to bugs in the
kernel-side thread support. `nscd' happens to hit these bugs
@@ -382,7 +384,7 @@
Reporting Bugs
==============
-There are probably bugs in the GNU C library. There are certainly
+There are probably bugs in the GNU C Library. There are certainly
errors and omissions in this manual. If you report them, they will get
fixed. If you don't, no one will ever know about them and they will
remain unfixed for all eternity, if not longer.
@@ -396,14 +398,14 @@
To report a bug, first you must find it. With any luck, this will
be the hard part. Once you've found a bug, make sure it's really a
-bug. A good way to do this is to see if the GNU C library behaves the
+bug. A good way to do this is to see if the GNU C Library behaves the
same way some other C library does. If so, probably you are wrong and
the libraries are right (but not necessarily). If not, one of the
-libraries is probably wrong. It might not be the GNU library. Many
+libraries is probably wrong. It might not be the GNU C Library. Many
historical Unix C libraries permit things that we don't, such as
closing a file twice.
- If you think you have found some way in which the GNU C library does
+ If you think you have found some way in which the GNU C Library does
not conform to the ISO and POSIX standards (*note Standards and
Portability::), that is definitely a bug. Report it!
Modified: fsf/trunk/libc/Makefile
==============================================================================
--- fsf/trunk/libc/Makefile (original)
+++ fsf/trunk/libc/Makefile Wed Feb 29 00:02:39 2012
@@ -398,8 +398,8 @@
makeinfo --no-validate --plaintext --no-number-sections $< -o $@
-chmod a-w $@
endef
-INSTALL: manual/install.texi; $(format-me)
-NOTES: manual/creature.texi; $(format-me)
+INSTALL: manual/install.texi manual/macros.texi; $(format-me)
+NOTES: manual/creature.texi manual/macros.texi; $(format-me)
manual/dir-add.texi manual/dir-add.info: FORCE
$(MAKE) $(PARALLELMFLAGS) -C $(@D) $(@F)
FAQ: scripts/gen-FAQ.pl FAQ.in
Modified: fsf/trunk/libc/NEWS
==============================================================================
--- fsf/trunk/libc/NEWS (original)
+++ fsf/trunk/libc/NEWS Wed Feb 29 00:02:39 2012
@@ -9,11 +9,11 @@
* The following bugs are resolved with this release:
- 174, 350, 411, 2547, 2548, 3335, 4026, 4596, 4822, 5077, 5461, 5805, 5993,
- 6884, 6907, 9739, 9902, 10110, 10140, 10210, 11174, 11322, 11365, 11494,
- 12047, 13058, 13525, 13526, 13527, 13528, 13529, 13530, 13531, 13532,
- 13533, 13547, 13551, 13552, 13553, 13555, 13559, 13583, 13618, 13695,
- 13704, 13738
+ 174, 350, 411, 2547, 2548, 3335, 3992, 4026, 4596, 4822, 5077, 5461, 5805,
+ 5993, 6884, 6907, 9739, 9902, 10110, 10140, 10210, 11174, 11322, 11365,
+ 11494, 12047, 13058, 13525, 13526, 13527, 13528, 13529, 13530, 13531,
+ 13532, 13533, 13547, 13551, 13552, 13553, 13555, 13559, 13583, 13618,
+ 13637, 13695, 13704, 13738
* ISO C11 support:
Modified: fsf/trunk/libc/NOTES
==============================================================================
--- fsf/trunk/libc/NOTES (original)
+++ fsf/trunk/libc/NOTES Wed Feb 29 00:02:39 2012
@@ -164,9 +164,9 @@
-- Macro: _ISOC99_SOURCE
Until the revised ISO C standard is widely adopted the new features
- are not automatically enabled. The GNU libc nevertheless has a
- complete implementation of the new standard and to enable the new
- features the macro `_ISOC99_SOURCE' should be defined.
+ are not automatically enabled. The GNU C Library nevertheless has
+ a complete implementation of the new standard and to enable the
+ new features the macro `_ISOC99_SOURCE' should be defined.
-- Macro: _GNU_SOURCE
If you define this macro, everything is included: ISO C89,
@@ -184,7 +184,7 @@
Note that if you do this, you must link your program with the BSD
compatibility library by passing the `-lbsd-compat' option to the
- compiler or linker. *Note:* If you forget to do this, you may get
+ compiler or linker. *NB:* If you forget to do this, you may get
very strange errors at run time.
-- Macro: _REENTRANT
@@ -192,8 +192,8 @@
If you define one of these macros, reentrant versions of several
functions get declared. Some of the functions are specified in
POSIX.1c but many others are only available on a few other systems
- or are unique to GNU libc. The problem is the delay in the
- standardization of the thread safe C library interface.
+ or are unique to the GNU C Library. The problem is the delay in
+ the standardization of the thread safe C library interface.
Unlike on some other systems, no special version of the C library
must be used for linking. There is only one version but while
Modified: fsf/trunk/libc/include/dirent.h
==============================================================================
--- fsf/trunk/libc/include/dirent.h (original)
+++ fsf/trunk/libc/include/dirent.h Wed Feb 29 00:02:39 2012
@@ -1,7 +1,9 @@
#ifndef _DIRENT_H
+# ifndef _ISOMAC
+# include <dirstream.h>
+# endif
# include <dirent/dirent.h>
# ifndef _ISOMAC
-# include <dirstream.h>
# include <sys/stat.h>
# include <stdbool.h>
Modified: fsf/trunk/libc/manual/arith.texi
==============================================================================
--- fsf/trunk/libc/manual/arith.texi (original)
+++ fsf/trunk/libc/manual/arith.texi Wed Feb 29 00:02:39 2012
@@ -40,9 +40,9 @@
of integers, and sometimes must be written for a particular size of
storage, regardless of what machine the program runs on.
-To address this problem, the GNU C library contains C type definitions
+To address this problem, @theglibc{} contains C type definitions
you can use to declare integers that meet your exact needs. Because the
-GNU C library header files are customized to a specific machine, your
+@glibcadj{} header files are customized to a specific machine, your
program source code doesn't have to be.
These @code{typedef}s are in @file{stdint.h}.
@@ -105,7 +105,7 @@
@item uintmax_t
@end itemize
-The GNU C library also provides macros that tell you the maximum and
+@Theglibc{} also provides macros that tell you the maximum and
minimum possible values for each integer data type. The macro names
follow these examples: @code{INT32_MAX}, @code{UINT8_MAX},
@code{INT_FAST32_MIN}, @code{INT_LEAST64_MIN}, @code{UINTMAX_MAX},
@@ -388,7 +388,7 @@
@end deftypefn
Another set of floating-point classification functions was provided by
-BSD. The GNU C library also supports these functions; however, we
+BSD. @Theglibc{} also supports these functions; however, we
recommend that you use the ISO C99 macros in new code. Those are standard
and will be available more widely. Also, since they are macros, you do
not have to worry about the type of their argument.
@@ -1019,7 +1019,7 @@
having type @code{fenv_t *}.
@vindex FE_NOMASK_ENV
-If possible, the GNU C Library defines a macro @code{FE_NOMASK_ENV}
+If possible, @theglibc{} defines a macro @code{FE_NOMASK_ENV}
which represents an environment where every exception raised causes a
trap to occur. You can test for this macro using @code{#ifdef}. It is
only defined if @code{_GNU_SOURCE} is defined.
@@ -1813,7 +1813,7 @@
@file{math.h} defines the symbols @code{FP_FAST_FMA},
@code{FP_FAST_FMAF}, and @code{FP_FAST_FMAL} when the corresponding
version of @code{fma} is no slower than the expression @samp{x*y + z}.
-In the GNU C library, this always means the operation is implemented in
+In @theglibc{}, this always means the operation is implemented in
hardware.
@end deftypefun
@@ -2445,7 +2445,7 @@
@code{strtod} is more robust.
@end deftypefun
-The GNU C library also provides @samp{_l} versions of these functions,
+@Theglibc{} also provides @samp{_l} versions of these functions,
which take an additional argument, the locale to use in conversion.
@xref{Parsing of Integers}.
@@ -2453,10 +2453,10 @@
@section Old-fashioned System V number-to-string functions
The old @w{System V} C library provided three functions to convert
-numbers to strings, with unusual and hard-to-use semantics. The GNU C
-library also provides these functions and some natural extensions.
-
-These functions are only available in glibc and on systems descended
+numbers to strings, with unusual and hard-to-use semantics. @Theglibc{}
+also provides these functions and some natural extensions.
+
+These functions are only available in @theglibc{} and on systems descended
from AT&T Unix. Therefore, unless these functions do precisely what you
need, it is better to use @code{sprintf}, which is standard.
@@ -2516,7 +2516,7 @@
@code{double} it is reduced to a system-specific value.
@end deftypefun
-As extensions, the GNU C library provides versions of these three
+As extensions, @theglibc{} provides versions of these three
functions that take @code{long double} arguments.
@comment stdlib.h
@@ -2547,7 +2547,7 @@
@cindex gcvt_r
The @code{ecvt} and @code{fcvt} functions, and their @code{long double}
equivalents, all return a string located in a static buffer which is
-overwritten by the next call to the function. The GNU C library
+overwritten by the next call to the function. @Theglibc{}
provides another set of extended functions which write the converted
string into a user-supplied buffer. These have the conventional
@code{_r} suffix.
Modified: fsf/trunk/libc/manual/charset.texi
==============================================================================
--- fsf/trunk/libc/manual/charset.texi (original)
+++ fsf/trunk/libc/manual/charset.texi Wed Feb 29 00:02:39 2012
@@ -361,7 +361,7 @@
The functions handling more than one character at a time require NUL
terminated strings as the argument (i.e., converting blocks of text
does not work unless one can add a NUL byte at an appropriate place).
-The GNU C library contains some extensions to the standard that allow
+@Theglibc{} contains some extensions to the standard that allow
specifying a size, but basically they also expect terminated strings.
@end itemize
@@ -418,7 +418,7 @@
maximum number of bytes in a multibyte character in the current locale.
The value is never greater than @code{MB_LEN_MAX}. Unlike
@code{MB_LEN_MAX} this macro need not be a compile-time constant, and in
-the GNU C library it is not.
+@theglibc{} it is not.
@pindex stdlib.h
@code{MB_CUR_MAX} is defined in @file{stdlib.h}.
@@ -793,7 +793,7 @@
Therefore, the @code{mbrlen} function will never read invalid memory.
Now that this function is available (just to make this clear, this
-function is @emph{not} part of the GNU C library) we can compute the
+function is @emph{not} part of @theglibc{}) we can compute the
number of wide character required to store the converted multibyte
character string @var{s} using
@@ -949,7 +949,7 @@
character at a time. Most operations to be performed in real-world
programs include strings and therefore the @w{ISO C} standard also
defines conversions on entire strings. However, the defined set of
-functions is quite limited; therefore, the GNU C library contains a few
+functions is quite limited; therefore, @theglibc{} contains a few
extensions that can help in some important situations.
@comment wchar.h
@@ -1030,7 +1030,7 @@
The generic conversion interface (@pxref{Generic Charset Conversion})
does not have this limitation (it simply works on buffers, not
-strings), and the GNU C library contains a set of functions that take
+strings), and @theglibc{} contains a set of functions that take
additional parameters specifying the maximal number of bytes that are
consumed from the input string. This way the problem of
@code{mbsrtowcs}'s example above could be solved by determining the line
@@ -1528,8 +1528,8 @@
common that they operate on character sets that are not directly
specified by the functions. The multibyte encoding used is specified by
the currently selected locale for the @code{LC_CTYPE} category. The
-wide character set is fixed by the implementation (in the case of GNU C
-library it is always UCS-4 encoded @w{ISO 10646}.
+wide character set is fixed by the implementation (in the case of @theglibc{}
+it is always UCS-4 encoded @w{ISO 10646}.
This has of course several problems when it comes to general character
conversion:
@@ -1648,7 +1648,7 @@
new descriptor must be created. The descriptor does not stand for all
of the conversions from @var{fromset} to @var{toset}.
-The GNU C library implementation of @code{iconv_open} has one
+The @glibcadj{} implementation of @code{iconv_open} has one
significant extension to other implementations. To ease the extension
of the set of available conversions, the implementation allows storing
the necessary files with data and code in an arbitrary number of
@@ -1740,7 +1740,7 @@
any assumption as to whether the conversion has to deal with states.
Even if the input and output character sets are not stateful, the
implementation might still have to keep states. This is due to the
-implementation chosen for the GNU C library as it is described below.
+implementation chosen for @theglibc{} as it is described below.
Therefore an @code{iconv} call to reset the state should always be
performed if some protocol requires this for the output text.
@@ -1761,7 +1761,7 @@
almost arbitrary, there can be situations where the input buffer contains
valid characters, which have no identical representation in the output
character set. The behavior in this situation is undefined. The
-@emph{current} behavior of the GNU C library in this situation is to
+@emph{current} behavior of @theglibc{} in this situation is to
return with an error immediately. This certainly is not the most
desirable solution; therefore, future versions will provide better ones,
but they are not yet finished.
@@ -1980,7 +1980,7 @@
limiting on some platforms since not many platforms support dynamic
loading in statically linked programs. On platforms without this
capability it is therefore not possible to use this interface in
-statically linked programs. The GNU C library has, on ELF platforms, no
+statically linked programs. @Theglibc{} has, on ELF platforms, no
problems with dynamic loading in these situations; therefore, this
point is moot. The danger is that one gets acquainted with this
situation and forgets about the restrictions on other systems.
@@ -2054,38 +2054,38 @@
routes.
@node glibc iconv Implementation
-@subsection The @code{iconv} Implementation in the GNU C library
+@subsection The @code{iconv} Implementation in @theglibc{}
After reading about the problems of @code{iconv} implementations in the
last section it is certainly good to note that the implementation in
-the GNU C library has none of the problems mentioned above. What
+@theglibc{} has none of the problems mentioned above. What
follows is a step-by-step analysis of the points raised above. The
evaluation is based on the current state of the development (as of
January 1999). The development of the @code{iconv} functions is not
complete, but basic functionality has solidified.
-The GNU C library's @code{iconv} implementation uses shared loadable
+@Theglibc{}'s @code{iconv} implementation uses shared loadable
modules to implement the conversions. A very small number of
conversions are built into the library itself but these are only rather
trivial conversions.
-All the benefits of loadable modules are available in the GNU C library
+All the benefits of loadable modules are available in the @glibcadj{}
implementation. This is especially appealing since the interface is
well documented (see below), and it, therefore, is easy to write new
conversion modules. The drawback of using loadable objects is not a
-problem in the GNU C library, at least on ELF systems. Since the
+problem in @theglibc{}, at least on ELF systems. Since the
library is able to load shared objects even in statically linked
binaries, static linking need not be forbidden in case one wants to use
@code{iconv}.
The second mentioned problem is the number of supported conversions.
-Currently, the GNU C library supports more than 150 character sets. The
+Currently, @theglibc{} supports more than 150 character sets. The
way the implementation is designed the number of supported conversions
is greater than 22350 (@math{150} times @math{149}). If any conversion
from or to a character set is missing, it can be added easily.
Particularly impressive as it may be, this high number is due to the
-fact that the GNU C library implementation of @code{iconv} does not have
+fact that the @glibcadj{} implementation of @code{iconv} does not have
the third problem mentioned above (i.e., whenever there is a conversion
from a character set @math{@cal{A}} to @math{@cal{B}} and from
@math{@cal{B}} to @math{@cal{C}} it is always possible to convert from
@@ -2115,7 +2115,7 @@
are much more similar to each other than to @w{ISO 10646}.
In such a situation one easily can write a new conversion and provide it
-as a better alternative. The GNU C library @code{iconv} implementation
+as a better alternative. The @glibcadj{} @code{iconv} implementation
would automatically use the module implementing the conversion if it is
specified to be more efficient.
@@ -2207,7 +2207,7 @@
conversion with only the cost of @math{1}.
A mysterious item about the @file{gconv-modules} file above (and also
-the file coming with the GNU C library) are the names of the character
+the file coming with @theglibc{}) are the names of the character
sets specified in the @code{module} lines. Why do almost all the names
end in @code{//}? And this is not all: the names can actually be
regular expressions. At this point in time this mystery should not be
@@ -2423,7 +2423,7 @@
It is often the case that one conversion is used more than once (i.e.,
there are several @code{iconv_open} calls for the same set of character
sets during one program run). The @code{mbsrtowcs} et.al.@: functions in
-the GNU C library also use the @code{iconv} functionality, which
+@theglibc{} also use the @code{iconv} functionality, which
increases the number of uses of the same functions even more.
Because of this multiple use of conversions, the modules do not get
@@ -2888,8 +2888,8 @@
@end deftypevr
This information should be sufficient to write new modules. Anybody
-doing so should also take a look at the available source code in the GNU
-C library sources. It contains many examples of working and optimized
+doing so should also take a look at the available source code in the
+@glibcadj{} sources. It contains many examples of working and optimized
modules.
@c File charset.texi edited October 2001 by Dennis Grace, IBM Corporation
Modified: fsf/trunk/libc/manual/conf.texi
==============================================================================
--- fsf/trunk/libc/manual/conf.texi (original)
+++ fsf/trunk/libc/manual/conf.texi Wed Feb 29 00:02:39 2012
@@ -147,7 +147,7 @@
POSIX defines certain system-specific options that not all POSIX systems
support. Since these options are provided in the kernel, not in the
-library, simply using the GNU C library does not guarantee any of these
+library, simply using @theglibc{} does not guarantee any of these
features is supported; it depends on the system you are using.
@pindex unistd.h
@@ -190,7 +190,7 @@
@comment POSIX.2
@deftypevr Macro int _POSIX2_C_DEV
If this symbol is defined, it indicates that the system has the POSIX.2
-C compiler command, @code{c89}. The GNU C library always defines this
+C compiler command, @code{c89}. @Theglibc{} always defines this
as @code{1}, on the assumption that you would not have installed it if
you didn't have a C compiler.
@end deftypevr
@@ -199,7 +199,7 @@
@comment POSIX.2
@deftypevr Macro int _POSIX2_FORT_DEV
If this symbol is defined, it indicates that the system has the POSIX.2
-Fortran compiler command, @code{fort77}. The GNU C library never
+Fortran compiler command, @code{fort77}. @Theglibc{} never
defines this, because we don't know what the system has.
@end deftypevr
@@ -207,15 +207,15 @@
@comment POSIX.2
@deftypevr Macro int _POSIX2_FORT_RUN
If this symbol is defined, it indicates that the system has the POSIX.2
-@code{asa} command to interpret Fortran carriage control. The GNU C
-library never defines this, because we don't know what the system has.
+@code{asa} command to interpret Fortran carriage control. @Theglibc{}
+never defines this, because we don't know what the system has.
@end deftypevr
@comment unistd.h
@comment POSIX.2
@deftypevr Macro int _POSIX2_LOCALEDEF
If this symbol is defined, it indicates that the system has the POSIX.2
-@code{localedef} command. The GNU C library never defines this, because
+@code{localedef} command. @Theglibc{} never defines this, because
we don't know what the system has.
@end deftypevr
@@ -223,7 +223,7 @@
@comment POSIX.2
@deftypevr Macro int _POSIX2_SW_DEV
If this symbol is defined, it indicates that the system has the POSIX.2
-commands @code{ar}, @code{make}, and @code{strip}. The GNU C library
+commands @code{ar}, @code{make}, and @code{strip}. @Theglibc{}
always defines this as @code{1}, on the assumption that you had to have
@code{ar} and @code{make} to install the library, and it's unlikely that
@code{strip} would be absent when those are present.
@@ -728,7 +728,7 @@
@item _SC_EQUIV_CLASS_MAX
Inquire about the maximum number of weights that can be assigned to an
entry of the @code{LC_COLLATE} category @samp{order} keyword in a locale
-definition. The GNU C library does not presently support locale
+definition. @Theglibc{} does not presently support locale
definitions.
@comment unistd.h
@@ -1198,7 +1198,7 @@
POSIX defines certain system-specific options in the system calls for
operating on files. Some systems support these options and others do
not. Since these options are provided in the kernel, not in the
-library, simply using the GNU C library does not guarantee that any of these
+library, simply using @theglibc{} does not guarantee that any of these
features is supported; it depends on the system you are using. They can
also vary between file systems on a single machine.
@@ -1210,11 +1210,10 @@
any other value indicates yes.) If the macro is undefined, it means
particular files may or may not support the feature.
-Since all the machines that support the GNU C library also support NFS,
+Since all the machines that support @theglibc{} also support NFS,
one can never make a general statement about whether all file systems
support the @code{_POSIX_CHOWN_RESTRICTED} and @code{_POSIX_NO_TRUNC}
-features. So these names are never defined as macros in the GNU C
-library.
+features. So these names are never defined as macros in @theglibc{}.
@comment unistd.h
@comment POSIX.1
@@ -1482,7 +1481,7 @@
through @code{sysconf} that apply to utility behavior rather than the
behavior of the library or the operating system.
-The GNU C library defines macros for these limits, and @code{sysconf}
+@Theglibc{} defines macros for these limits, and @code{sysconf}
returns values for them if you ask; but these values convey no
meaningful information. They are simply the smallest values that
POSIX.2 permits.
@@ -1543,7 +1542,7 @@
@deftypevr Macro int EQUIV_CLASS_MAX
The maximum number of weights that can be assigned to an entry of the
@code{LC_COLLATE} category @samp{order} keyword in a locale definition.
-The GNU C library does not presently support locale definitions.
+@Theglibc{} does not presently support locale definitions.
@end deftypevr
@node Utility Minimums
@@ -1601,7 +1600,7 @@
The most restrictive limit permitted by POSIX.2 for the maximum number
of weights that can be assigned to an entry of the @code{LC_COLLATE}
category @samp{order} keyword in a locale definition. Its value is
-@code{2}. The GNU C library does not presently support locale
+@code{2}. @Theglibc{} does not presently support locale
definitions.
@end table
Modified: fsf/trunk/libc/manual/contrib.texi
==============================================================================
--- fsf/trunk/libc/manual/contrib.texi (original)
+++ fsf/trunk/libc/manual/contrib.texi Wed Feb 29 00:02:39 2012
@@ -1,8 +1,8 @@
@node Contributors, Free Manuals, Maintenance, Top
-@c %MENU% Who wrote what parts of the GNU C library
-@appendix Contributors to the GNU C Library
-
-The GNU C library was written originally by Roland McGrath, and is
+@c %MENU% Who wrote what parts of the GNU C Library
+@appendix Contributors to @theglibc{}
+
+@Theglibc{} was written originally by Roland McGrath, and is
currently maintained by Ulrich Drepper. Some parts of the library were
contributed or worked on by other people.
@@ -93,7 +93,7 @@
@item
The port to Linux i386/ELF (@code{i386-@var{anything}-linux}) was
contributed by Ulrich Drepper, based in large part on work done in
-Hongjiu Lu's Linux version of the GNU C Library.
+Hongjiu Lu's Linux version of @theglibc{}.
@item
The port to Linux/m68k (@code{m68k-@var{anything}-linux}) was
@@ -178,7 +178,7 @@
@code{rand} and @code{srand} functions, were written by Earl T. Cohen
for the University of California at Berkeley and are copyrighted by the
Regents of the University of California. They have undergone minor
-changes to fit into the GNU C library and to fit the @w{ISO C} standard,
+changes to fit into @theglibc{} and to fit the @w{ISO C} standard,
but the functional code is Berkeley's.@refill
@item
Modified: fsf/trunk/libc/manual/creature.texi
==============================================================================
--- fsf/trunk/libc/manual/creature.texi (original)
+++ fsf/trunk/libc/manual/creature.texi Wed Feb 29 00:02:39 2012
@@ -1,5 +1,6 @@
@node Feature Test Macros
@subsection Feature Test Macros
+@include macros.texi
@cindex feature test macros
The exact set of features available when you compile a source file
@@ -65,7 +66,7 @@
Greater values for @code{_POSIX_C_SOURCE} will enable future extensions.
The POSIX standards process will define these values as necessary, and
-the GNU C Library should support them some time after they become standardized.
+@theglibc{} should support them some time after they become standardized.
The 1996 edition of POSIX.1 (ISO/IEC 9945-1: 1996) states that
if you define @code{_POSIX_C_SOURCE} to a value greater than
or equal to @code{199506L}, then the functionality from the 1996
@@ -192,7 +193,7 @@
@comment GNU
@defvr Macro _ISOC99_SOURCE
Until the revised @w{ISO C} standard is widely adopted the new features
-are not automatically enabled. The GNU libc nevertheless has a complete
+are not automatically enabled. @Theglibc{} nevertheless has a complete
implementation of the new standard and to enable the new features the
macro @code{_ISOC99_SOURCE} should be defined.
@end defvr
@@ -227,7 +228,7 @@
@defvrx Macro _THREAD_SAFE
If you define one of these macros, reentrant versions of several functions get
declared. Some of the functions are specified in POSIX.1c but many others
-are only available on a few other systems or are unique to GNU libc.
+are only available on a few other systems or are unique to @theglibc{}.
The problem is the delay in the standardization of the thread safe C library
interface.
Modified: fsf/trunk/libc/manual/crypt.texi
==============================================================================
--- fsf/trunk/libc/manual/crypt.texi (original)
+++ fsf/trunk/libc/manual/crypt.texi Wed Feb 29 00:02:39 2012
@@ -23,7 +23,7 @@
work out what its input was by looking at its output, before storing in
the file.
-The GNU C library provides a one-way function that is compatible with
+@Theglibc{} provides a one-way function that is compatible with
the behavior of the @code{crypt} function introduced in FreeBSD 2.0.
It supports two one-way algorithms: one based on the MD5
message-digest algorithm that is compatible with modern BSD systems,
@@ -103,7 +103,7 @@
characters of a mistyped password are not accidentally visible.
In other C libraries, @code{getpass} may only return the first
-@code{PASS_MAX} bytes of a password. The GNU C library has no limit, so
+@code{PASS_MAX} bytes of a password. @Theglibc{} has no limit, so
@code{PASS_MAX} is undefined.
The prototype for this function is in @file{unistd.h}. @code{PASS_MAX}
Modified: fsf/trunk/libc/manual/ctype.texi
==============================================================================
--- fsf/trunk/libc/manual/ctype.texi (original)
+++ fsf/trunk/libc/manual/ctype.texi Wed Feb 29 00:02:39 2012
@@ -273,7 +273,7 @@
is more general. It allows extensions to the set of available
classifications, beyond those which are always available. The POSIX
standard specifies how extensions can be made, and this is already
-implemented in the GNU C library implementation of the @code{localedef}
+implemented in the @glibcadj{} implementation of the @code{localedef}
program.
The character class functions are normally implemented with bitsets,
@@ -589,7 +589,7 @@
It is declared in @file{wctype.h}.
@end deftypefun
-The GNU C library also provides a function which is not defined in the
+@Theglibc{} also provides a function which is not defined in the
@w{ISO C} standard but which is available as a version for single byte
characters as well.
@@ -607,7 +607,7 @@
The first note is probably not astonishing but still occasionally a
cause of problems. The @code{isw@var{XXX}} functions can be implemented
-using macros and in fact, the GNU C library does this. They are still
+using macros and in fact, @theglibc{} does this. They are still
available as real functions but when the @file{wctype.h} header is
included the macros will be used. This is the same as the
@code{char} type versions of these functions.
Modified: fsf/trunk/libc/manual/errno.texi
==============================================================================
--- fsf/trunk/libc/manual/errno.texi (original)
+++ fsf/trunk/libc/manual/errno.texi Wed Feb 29 00:02:39 2012
@@ -6,7 +6,7 @@
@cindex error codes
@cindex status codes
-Many functions in the GNU C library detect and report error conditions,
+Many functions in @theglibc{} detect and report error conditions,
and sometimes your programs need to check for these error conditions.
For example, when you open an input file, you should verify that the
file was actually opened correctly, and print an error message or take
@@ -67,7 +67,7 @@
``modifiable lvalue'' rather than as a variable, permitting it to be
implemented as a macro. For example, its expansion might involve a
function call, like @w{@code{*_errno ()}}. In fact, that is what it is
-on the GNU system itself. The GNU library, on non-GNU systems, does
+on the GNU system itself. @Theglibc{}, on non-GNU systems, does
whatever is right for the particular system.
There are a few library functions, like @code{sqrt} and @code{atan},
@@ -114,8 +114,8 @@
@pindex errno.h
The error code macros are defined in the header file @file{errno.h}.
All of them expand into integer constant values. Some of these error
-codes can't occur on the GNU system, but they can occur using the GNU
-library on other systems.
+codes can't occur on the GNU system, but they can occur using @theglibc{}
+on other systems.
@comment errno.h
@comment POSIX.1: Operation not permitted
@@ -419,7 +419,7 @@
@comment errno 35 @c DO NOT REMOVE
Resource temporarily unavailable; the call might work if you try again
later. The macro @code{EWOULDBLOCK} is another name for @code{EAGAIN};
-they are always the same in the GNU C library.
+they are always the same in @theglibc{}.
This error can happen in a few different situations:
@@ -452,7 +452,7 @@
@comment BSD: Operation would block
@deftypevr Macro int EWOULDBLOCK
@comment errno EAGAIN @c DO NOT REMOVE
-In the GNU C library, this is another name for @code{EAGAIN} (above).
+In @theglibc{}, this is another name for @code{EAGAIN} (above).
The values are always the same, on every operating system.
C libraries in many older Unix systems have @code{EWOULDBLOCK} as a
@@ -1572,7 +1572,7 @@
@code{error} and @code{error_at_line} are clearly the functions of
choice and enable the programmer to write applications which follow the
-GNU coding standard. The GNU libc additionally contains functions which
+GNU coding standard. @Theglibc{} additionally contains functions which
are used in BSD for the same purpose. These functions are declared in
@file{err.h}. It is generally advised to not use these functions. They
are included only for compatibility.
Modified: fsf/trunk/libc/manual/filesys.texi
==============================================================================
--- fsf/trunk/libc/manual/filesys.texi (original)
+++ fsf/trunk/libc/manual/filesys.texi Wed Feb 29 00:02:39 2012
@@ -2,7 +2,7 @@
@c %MENU% Functions for manipulating files
@chapter File System Interface
-This chapter describes the GNU C library's functions for manipulating
+This chapter describes @theglibc{}'s functions for manipulating
files. Unlike the input and output functions (@pxref{I/O on Streams};
@pxref{Low-Level I/O}), these functions are concerned with operating
on the files themselves rather than on their contents.
@@ -63,7 +63,7 @@
@var{buffer} that you provide. The @var{size} argument is how you tell
the system the allocation size of @var{buffer}.
-The GNU library version of this function also permits you to specify a
+The @glibcadj{} version of this function also permits you to specify a
null pointer for the @var{buffer} argument. Then @code{getcwd}
allocates a buffer automatically, as with @code{malloc}
(@pxref{Unconstrained Allocation}). If the @var{size} is greater than
@@ -117,7 +117,7 @@
@comment BSD
@deftypefn {Deprecated Function} {char *} getwd (char *@var{buffer})
This is similar to @code{getcwd}, but has no way to specify the size of
-the buffer. The GNU library provides @code{getwd} only
+the buffer. @Theglibc{} provides @code{getwd} only
for backwards compatibility with BSD.
The @var{buffer} argument should be a pointer to an array at least
@@ -413,7 +413,7 @@
to switch the current working directory to the directory just read the
@code{fchdir} function could be used. Historically the @code{DIR} type
was exposed and programs could access the fields. This does not happen
-in the GNU C library. Instead a separate function is provided to allow
+in @theglibc{}. Instead a separate function is provided to allow
access.
@comment dirent.h
@@ -634,7 +634,7 @@
As described above the fourth argument to the @code{scandir} function
must be a pointer to a sorting function. For the convenience of the
-programmer the GNU C library contains implementations of functions which
+programmer @theglibc{} contains implementations of functions which
are very helpful for this purpose.
@comment dirent.h
@@ -3035,7 +3035,7 @@
@cindex special files
The @code{mknod} function is the primitive for making special files,
-such as files that correspond to devices. The GNU library includes
+such as files that correspond to devices. @Theglibc{} includes
this function for compatibility with BSD.
The prototype for @code{mknod} is declared in @file{sys/stat.h}.
@@ -3176,7 +3176,7 @@
@code{tmpnam} at least this many times before it might fail saying you
have made too many temporary file names.
-With the GNU library, you can create a very large number of temporary
+With @theglibc{}, you can create a very large number of temporary
file names. If you actually created the files, you would probably run
out of disk space before you ran out of names. Some other systems have
a fixed, small limit on the number of temporary files. The limit is
Modified: fsf/trunk/libc/manual/header.texi
==============================================================================
--- fsf/trunk/libc/manual/header.texi (original)
+++ fsf/trunk/libc/manual/header.texi Wed Feb 29 00:02:39 2012
@@ -3,7 +3,7 @@
@appendix Summary of Library Facilities
This appendix is a complete list of the facilities declared within the
-header files supplied with the GNU C library. Each entry also lists the
+header files supplied with @theglibc{}. Each entry also lists the
standard or other source from which each facility is derived, and tells
you where in the manual you can find more information about how to use
it.
Modified: fsf/trunk/libc/manual/install.texi
==============================================================================
--- fsf/trunk/libc/manual/install.texi (original)
+++ fsf/trunk/libc/manual/install.texi Wed Feb 29 00:02:39 2012
@@ -1,17 +1,18 @@
@c This is for making the `INSTALL' file for the distribution.
@c Makeinfo ignores it when processing the file from the include.
@setfilename INSTALL
+@include macros.texi
@node Installation, Maintenance, Library Summary, Top
-@c %MENU% How to install the GNU C library
-@appendix Installing the GNU C Library
+@c %MENU% How to install the GNU C Library
+@appendix Installing @theglibc{}
Before you do anything else, you should read the file @file{FAQ} located
at the top level of the source tree. This file answers common questions
and describes problems you may experience with compilation and
installation. It is updated more frequently than this manual.
-Features can be added to GNU Libc via @dfn{add-on} bundles. These are
+Features can be added to @theglibc{} via @dfn{add-on} bundles. These are
separate tar files, which you unpack into the top level of the source
tree. Then you give @code{configure} the @samp{--enable-add-ons} option
to activate them, and they will be compiled into the library.
@@ -29,13 +30,14 @@
@end menu
@node Configuring and compiling
-@appendixsec Configuring and compiling GNU Libc
+@appendixsec Configuring and compiling @theglibc{}
@cindex configuring
@cindex compiling
-GNU libc cannot be compiled in the source directory. You must build
+@Theglibc{} cannot be compiled in the source directory. You must build
it in a separate build directory. For example, if you have unpacked
-the glibc sources in @file{/src/gnu/glibc-@var{version}}, create a directory
+the @glibcadj{} sources in @file{/src/gnu/glibc-@var{version}},
+create a directory
@file{/src/gnu/glibc-build} to put the object files in. This allows
removing the whole build directory in case an error occurs, which is
the safest way to get a fresh start and should always be done.
@@ -54,7 +56,7 @@
@noindent
@code{configure} takes many options, but the only one that is usually
mandatory is @samp{--prefix}. This option tells @code{configure}
-where you want glibc installed. This defaults to @file{/usr/local},
+where you want @theglibc{} installed. This defaults to @file{/usr/local},
but the normal setting to install as the standard system library is
@samp{--prefix=/usr} for GNU/Linux systems and @samp{--prefix=} (an
empty prefix) for GNU/Hurd systems.
@@ -79,15 +81,15 @@
@item --with-headers=@var{directory}
Look for kernel header files in @var{directory}, not
-@file{/usr/include}. Glibc needs information from the kernel's header
-files describing the interface to the kernel. Glibc will normally
+@file{/usr/include}. @Theglibc{} needs information from the kernel's header
+files describing the interface to the kernel. @Theglibc{} will normally
look in @file{/usr/include} for them,
but if you specify this option, it will look in @var{DIRECTORY} instead.
This option is primarily of use on a system where the headers in
-@file{/usr/include} come from an older version of glibc. Conflicts can
+@file{/usr/include} come from an older version of @theglibc{}. Conflicts can
occasionally happen in this case. You can also use this option if you want to
-compile glibc with a newer set of kernel headers than the ones found in
+compile @theglibc{} with a newer set of kernel headers than the ones found in
@file{/usr/include}.
@item --enable-add-ons[=@var{list}]
@@ -112,7 +114,7 @@
Use the binutils (assembler and linker) in @file{@var{directory}}, not
the ones the C compiler would default to. You can use this option if
the default binutils on your system cannot deal with all the constructs
-in the GNU C library. In that case, @code{configure} will detect the
+in @theglibc{}. In that case, @code{configure} will detect the
problem and suppress these constructs, so that the library will still be
usable, but functionality may be lost---for example, you can't build a
shared libc with old binutils.
@@ -156,7 +158,7 @@
@itemx --host=@var{host-system}
These options are for cross-compiling. If you specify both options and
@var{build-system} is different from @var{host-system}, @code{configure}
-will prepare to cross-compile glibc from @var{build-system} to be used
+will prepare to cross-compile @theglibc{} from @var{build-system} to be used
on @var{host-system}. You'll probably need the @samp{--with-headers}
option too, and you may have to override @var{configure}'s selection of
the compiler and/or binutils.
@@ -193,7 +195,7 @@
verifying that the problem is not already known. @xref{Reporting Bugs},
for instructions on reporting bugs. Note that some of the tests assume
they are not being run by @code{root}. We recommend you compile and
-test glibc as an unprivileged user.
+test @theglibc{} as an unprivileged user.
Before reporting bugs make sure there is no problem with your system.
The tests (and later installation) use some pre-existing files of the
@@ -213,7 +215,7 @@
for your system. The file is included and parsed by @code{make} and has
to follow the conventions for makefiles.
-It is easy to configure the GNU C library for cross-compilation by
+It is easy to configure @theglibc{} for cross-compilation by
setting a few variables in @file{configparms}. Set @code{CC} to the
cross-compiler for the target you configured the library for; it is
important to use this same @code{CC} value when running
@@ -232,13 +234,14 @@
To install the library and its header files, and the Info files of the
manual, type @code{env LANGUAGE=C LC_ALL=C make install}. This will
build things, if necessary, before installing them; however, you should
-still compile everything first. If you are installing glibc as your
+still compile everything first. If you are installing @theglibc{} as your
primary C library, we recommend that you shut the system down to
single-user mode first, and reboot afterward. This minimizes the risk
of breaking things when the library changes out from underneath.
@samp{make install} will do the entire job of upgrading from a
-previous installation of glibc 2.x. There may sometimes be headers
+previous installation of @theglibc{} version 2.x. There may sometimes
+be headers
left behind from the previous installation, but those are generally
harmless. If you want to avoid leaving headers behind you can do
things in the following order.
@@ -252,17 +255,17 @@
library. The new @file{/usr/include}, after switching the include
directories and before installing the library should contain the Linux
headers, but nothing else. If you do this, you will need to restore
-any headers from non-glibc libraries youself after installing the
+any headers from libraries other than @theglibc{} yourself after installing the
library.
-You can install glibc somewhere other than where you configured it to go
+You can install @theglibc{} somewhere other than where you configured it to go
by setting the @code{install_root} variable on the command line for
@samp{make install}. The value of this variable is prepended to all the
paths for installation. This is useful when setting up a chroot
environment or preparing a binary distribution. The directory should be
specified with an absolute file name.
-Glibc includes a daemon called @code{nscd}, which you
+@Theglibc{} includes a daemon called @code{nscd}, which you
may or may not want to run. @code{nscd} caches name service lookups; it
can dramatically improve performance with NIS+, and may help with DNS as
well.
@@ -278,11 +281,11 @@
The source for @file{pt_chown} is in @file{login/programs/pt_chown.c}.
After installation you might want to configure the timezone and locale
-installation of your system. The GNU C library comes with a locale
+installation of your system. @Theglibc{} comes with a locale
database which gets configured with @code{localedef}. For example, to
set up a German locale with name @code{de_DE}, simply issue the command
@samp{localedef -i de_DE -f ISO-8859-1 de_DE}. To configure all locales
-that are supported by glibc, you can issue from your build directory the
+that are supported by @theglibc{}, you can issue from your build directory the
command @samp{make localedata/install-locales}.
To configure the locally used timezone, set the @code{TZ} environment
@@ -300,14 +303,14 @@
@cindex tools, for installing library
We recommend installing the following GNU tools before attempting to
-build the GNU C library:
+build @theglibc{}:
@itemize @bullet
@item
GNU @code{make} 3.79 or newer
-You need the latest version of GNU @code{make}. Modifying the GNU C
-Library to work with other @code{make} programs would be so difficult that
+You need the latest version of GNU @code{make}. Modifying @theglibc{}
+to work with other @code{make} programs would be so difficult that
we recommend you port GNU @code{make} instead. @strong{Really.} We
recommend GNU @code{make} version 3.79. All earlier versions have severe
bugs or lack features.
@@ -316,17 +319,17 @@
GCC 4.3 or newer, GCC 4.6 recommended
GCC 4.3 or higher is required; as of this writing, GCC 4.6 is the
-compiler we advise to use to build the GNU C library.
-
-You can use whatever compiler you like to compile programs that use GNU
-libc.
+compiler we advise to use to build @theglibc{}.
+
+You can use whatever compiler you like to compile programs that use
+@theglibc{}.
Check the FAQ for any special compiler issues on particular platforms.
@item
GNU @code{binutils} 2.15 or later
-You must use GNU @code{binutils} (as and ld) to build the GNU C library.
+You must use GNU @code{binutils} (as and ld) to build @theglibc{}.
No other assembler or linker has the necessary functionality at the
moment.
@@ -386,41 +389,41 @@
@appendixsec Specific advice for GNU/Linux systems
@cindex kernel header files
-If you are installing GNU libc on a GNU/Linux system, you need to have
+If you are installing @theglibc{} on a GNU/Linux system, you need to have
the header files from a 2.6.19.1 or newer kernel around for reference.
These headers must be installed using @samp{make headers_install}; the
headers present in the kernel source directory are not suitable for
-direct use by GNU libc. You do not need to use that kernel, just have
-its headers installed where glibc can access them, referred to here as
+direct use by @theglibc{}. You do not need to use that kernel, just have
+its headers installed where @theglibc{} can access them, referred to here as
@var{install-directory}. The easiest way to do this is to unpack it
in a directory such as @file{/usr/src/linux-@var{version}}. In that
directory, run @samp{make headers_install
-INSTALL_HDR_PATH=@var{install-directory}}. Finally, configure glibc
+INSTALL_HDR_PATH=@var{install-directory}}. Finally, configure @theglibc{}
with the option @samp{--with-headers=@var{install-directory}/include}.
Use the most recent kernel you can get your hands on. (If you are
-cross-compiling GNU libc, you need to specify
+cross-compiling @theglibc{}, you need to specify
@samp{ARCH=@var{architecture}} in the @samp{make headers_install}
command, where @var{architecture} is the architecture name used by the
Linux kernel, such as @samp{x86} or @samp{powerpc}.)
-After installing GNU libc, you may need to remove or rename
+After installing @theglibc{}, you may need to remove or rename
directories such as @file{/usr/include/linux} and
@file{/usr/include/asm}, and replace them with copies of directories
such as @file{linux} and @file{asm} from
@file{@var{install-directory}/include}. All directories present in
@file{@var{install-directory}/include} should be copied, except that
-GNU libc provides its own version of @file{/usr/include/scsi}; the
+@theglibc{} provides its own version of @file{/usr/include/scsi}; the
files provided by the kernel should be copied without replacing those
-provided by GNU libc. The @file{linux}, @file{asm} and
+provided by @theglibc{}. The @file{linux}, @file{asm} and
@file{asm-generic} directories are required to compile programs using
-GNU libc; the other directories describe interfaces to the kernel but
+@theglibc{}; the other directories describe interfaces to the kernel but
are not required if not compiling programs using those interfaces.
You do not need to copy kernel headers if you did not specify an
alternate kernel header source using @samp{--with-headers}.
-GNU/Linux expects some components of the libc installation to be in
+GNU/Linux expects some components of the @glibcadj{} installation to be in
@file{/lib} and some in @file{/usr/lib}. This is handled automatically
-if you configure glibc with @samp{--prefix=/usr}. If you set some other
+if you configure @theglibc{} with @samp{--prefix=/usr}. If you set some other
prefix or allow it to default to @file{/usr/local}, then all the
components are installed there.
@@ -434,7 +437,7 @@
@cindex reporting bugs
@cindex bugs, reporting
-There are probably bugs in the GNU C library. There are certainly
+There are probably bugs in @theglibc{}. There are certainly
errors and omissions in this manual. If you report them, they will get
fixed. If you don't, no one will ever know about them and they will
remain unfixed for all eternity, if not longer.
@@ -449,14 +452,14 @@
To report a bug, first you must find it. With any luck, this will be the
hard part. Once you've found a bug, make sure it's really a bug. A
-good way to do this is to see if the GNU C library behaves the same way
+good way to do this is to see if @theglibc{} behaves the same way
some other C library does. If so, probably you are wrong and the
libraries are right (but not necessarily). If not, one of the libraries
-is probably wrong. It might not be the GNU library. Many historical
+is probably wrong. It might not be @theglibc{}. Many historical
Unix C libraries permit things that we don't, such as closing a file
twice.
-If you think you have found some way in which the GNU C library does not
+If you think you have found some way in which @theglibc{} does not
conform to the ISO and POSIX standards (@pxref{Standards and
Portability}), that is definitely a bug. Report it!
Modified: fsf/trunk/libc/manual/intro.texi
==============================================================================
--- fsf/trunk/libc/manual/intro.texi (original)
+++ fsf/trunk/libc/manual/intro.texi Wed Feb 29 00:02:39 2012
@@ -9,13 +9,13 @@
programs.
@cindex library
-The GNU C library, described in this document, defines all of the
+@Theglibc{}, described in this document, defines all of the
library functions that are specified by the @w{ISO C} standard, as well as
additional features specific to POSIX and other derivatives of the Unix
operating system, and extensions specific to the GNU system.
The purpose of this manual is to tell you how to use the facilities
-of the GNU library. We have mentioned which features belong to which
+of @theglibc{}. We have mentioned which features belong to which
standards to help you identify things that are potentially non-portable
to other systems. But the emphasis in this manual is not on strict
portability.
@@ -38,7 +38,7 @@
(@pxref{ISO C}), rather than ``traditional'' pre-ISO C dialects, is
assumed.
-The GNU C library includes several @dfn{header files}, each of which
+@Theglibc{} includes several @dfn{header files}, each of which
provides definitions and declarations for a group of related facilities;
this information is used by the C compiler when processing your program.
For example, the header file @file{stdio.h} declares facilities for
@@ -48,7 +48,7 @@
If you are reading this manual for the first time, you should read all
of the introductory material and skim the remaining chapters. There are
-a @emph{lot} of functions in the GNU C library and it's not realistic to
+a @emph{lot} of functions in @theglibc{} and it's not realistic to
expect that you will be able to remember exactly @emph{how} to use each
and every one of them. It's more important to become generally familiar
with the kinds of facilities that the library provides, so that when you
@@ -61,12 +61,12 @@
@section Standards and Portability
@cindex standards
-This section discusses the various standards and other sources that the
-GNU C library is based upon. These sources include the @w{ISO C} and
+This section discusses the various standards and other sources that @theglibc{}
+is based upon. These sources include the @w{ISO C} and
POSIX standards, and the System V and Berkeley Unix implementations.
The primary focus of this manual is to tell you how to make effective
-use of the GNU library facilities. But if you are concerned about
+use of the @glibcadj{} facilities. But if you are concerned about
making your programs compatible with these standards, or portable to
operating systems other than GNU, this can affect how you use the
library. This section gives you an overview of these standards, so that
@@ -91,14 +91,14 @@
@subsection ISO C
@cindex ISO C
-The GNU C library is compatible with the C standard adopted by the
+@Theglibc{} is compatible with the C standard adopted by the
American National Standards Institute (ANSI):
@cite{American National Standard X3.159-1989---``ANSI C''} and later
by the International Standardization Organization (ISO):
@cite{ISO/IEC 9899:1990, ``Programming languages---C''}.
We here refer to the standard as @w{ISO C} since this is the more
general standard in respect of ratification.
-The header files and library facilities that make up the GNU library are
+The header files and library facilities that make up @theglibc{} are
a superset of those specified by the @w{ISO C} standard.@refill
@pindex gcc
@@ -131,7 +131,7 @@
@cindex IEEE Std 1003.2
@cindex ISO/IEC 9945-2
-The GNU library is also compatible with the ISO @dfn{POSIX} family of
+@Theglibc{} is also compatible with the ISO @dfn{POSIX} family of
standards, known more formally as the @dfn{Portable Operating System
Interface for Computer Environments} (ISO/IEC 9945). They were also
published as ANSI/IEEE Std 1003. POSIX is derived mostly from various
@@ -146,7 +146,7 @@
programming language support which can run in many diverse operating
system environments.@refill
-The GNU C library implements all of the functions specified in
+@Theglibc{} implements all of the functions specified in
@cite{ISO/IEC 9945-1:1996, the POSIX System Application Program
Interface}, commonly referred to as POSIX.1. The primary extensions to
the @w{ISO C} facilities specified by this standard include file system
@@ -155,7 +155,7 @@
process control functions (@pxref{Processes}).
Some facilities from @cite{ISO/IEC 9945-2:1993, the POSIX Shell and
-Utilities standard} (POSIX.2) are also implemented in the GNU library.
+Utilities standard} (POSIX.2) are also implemented in @theglibc{}.
These include utilities for dealing with regular expressions and other
pattern matching facilities (@pxref{Pattern Matching}).
@@ -181,7 +181,7 @@
@cindex SunOS
@cindex Unix, Berkeley
-The GNU C library defines facilities from some versions of Unix which
+@Theglibc{} defines facilities from some versions of Unix which
are not formally standardized, specifically from the 4.2 BSD, 4.3 BSD,
and 4.4 BSD Unix systems (also known as @dfn{Berkeley Unix}) and from
@dfn{SunOS} (a popular 4.2 BSD derivative that includes some Unix System
@@ -202,7 +202,7 @@
the AT&T Unix System V operating system. It is to some extent a
superset of the POSIX standard (@pxref{POSIX}).
-The GNU C library defines most of the facilities required by the SVID
+@Theglibc{} defines most of the facilities required by the SVID
that are not also required by the @w{ISO C} or POSIX standards, for
compatibility with System V Unix and other Unix systems (such as
SunOS) which include these facilities. However, many of the more
@@ -222,7 +222,7 @@
the XPG specifies the requirements for systems which are intended to be
a Unix system.
-The GNU C library complies to the X/Open Portability Guide, Issue 4.2,
+@Theglibc{} complies to the X/Open Portability Guide, Issue 4.2,
with all extensions common to XSI (X/Open System Interface)
compliant systems and also all X/Open UNIX extensions.
@@ -238,7 +238,7 @@
@section Using the Library
This section describes some of the practical issues involved in using
-the GNU C library.
+@theglibc{}.
@menu
* Header Files:: How to include the header files in your
@@ -269,7 +269,7 @@
@cindex definition (compared to declaration)
@cindex declaration (compared to definition)
-In order to use the facilities in the GNU C library, you should be sure
+In order to use the facilities in @theglibc{}, you should be sure
that your program source files include the appropriate header files.
This is so that the compiler has declarations of these facilities
available and can correctly process references to them. Once your
@@ -310,7 +310,7 @@
directives, @pxref{Header Files,,, cpp.info, The GNU C Preprocessor
Manual}.@refill
-The GNU C library provides several header files, each of which contains
+@Theglibc{} provides several header files, each of which contains
the type and macro definitions and variable and function declarations
for a group of related facilities. This means that your programs may
need to include several header files, depending on exactly which
@@ -319,8 +319,8 @@
Some library header files include other library header files
automatically. However, as a matter of programming style, you should
not rely on this; it is better to explicitly include all the header
-files required for the library facilities you are using. The GNU C
-library header files have been written in such a way that it doesn't
+files required for the library facilities you are using. The @glibcadj{}
+header files have been written in such a way that it doesn't
matter if a header file is accidentally included more than once;
including a header file a second time has no effect. Likewise, if your
program needs to include multiple header files, the order in which they
@@ -572,7 +572,7 @@
have diagnostic messages printed if the tests fail.
@item
-@ref{Memory}, describes the GNU library's facilities for managing and
+@ref{Memory}, describes @theglibc{}'s facilities for managing and
using virtual and real memory, including dynamic allocation of virtual
memory. If you do not know in advance how much memory your program
needs, you can allocate it dynamically instead, and manipulate it via
@@ -714,7 +714,7 @@
and says what standard or system each is derived from.
@item
-@ref{Installation}, explains how to build and install the GNU C library on
+@ref{Installation}, explains how to build and install @theglibc{} on
your system, and how to report any bugs you might find.
@item
Modified: fsf/trunk/libc/manual/io.texi
==============================================================================
--- fsf/trunk/libc/manual/io.texi (original)
+++ fsf/trunk/libc/manual/io.texi Wed Feb 29 00:02:39 2012
@@ -3,8 +3,8 @@
@chapter Input/Output Overview
Most programs need to do either input (reading data) or output (writing
-data), or most frequently both, in order to do anything useful. The GNU
-C library provides such a large selection of input and output functions
+data), or most frequently both, in order to do anything useful. @Theglibc{}
+provides such a large selection of input and output functions
that the hardest part is often deciding which function is most
appropriate!
@@ -65,7 +65,7 @@
output operations on it.
@menu
-* Streams and File Descriptors:: The GNU Library provides two ways
+* Streams and File Descriptors:: The GNU C Library provides two ways
to access the contents of files.
* File Position:: The number of bytes from the
beginning of the file.
@@ -123,8 +123,8 @@
portable as streams. You can expect any system running @w{ISO C} to
support streams, but non-GNU systems may not support file descriptors at
all, or may only implement a subset of the GNU functions that operate on
-file descriptors. Most of the file descriptor functions in the GNU
-library are included in the POSIX.1 standard, however.
+file descriptors. Most of the file descriptor functions in @theglibc{}
+are included in the POSIX.1 standard, however.
@node File Position, , Streams and File Descriptors, I/O Concepts
@subsection File Position
@@ -236,7 +236,7 @@
@subsection File Name Resolution
A file name consists of file name components separated by slash
-(@samp{/}) characters. On the systems that the GNU C library supports,
+(@samp{/}) characters. On the systems that @theglibc{} supports,
multiple successive @samp{/} characters are equivalent to a single
@samp{/} character.
Modified: fsf/trunk/libc/manual/job.texi
==============================================================================
--- fsf/trunk/libc/manual/job.texi (original)
+++ fsf/trunk/libc/manual/job.texi Wed Feb 29 00:02:39 2012
@@ -107,7 +107,7 @@
@cindex job control is optional
Not all operating systems support job control. The GNU system does
-support job control, but if you are using the GNU library on some other
+support job control, but if you are using @theglibc{} on some other
system, that system may not support job control itself.
You can use the @code{_POSIX_JOB_CONTROL} macro to test at compile-time
@@ -1026,7 +1026,7 @@
@cindex controlling terminal, determining
You can use the @code{ctermid} function to get a file name that you can
-use to open the controlling terminal. In the GNU library, it returns
+use to open the controlling terminal. In @theglibc{}, it returns
the same string all the time: @code{"/dev/tty"}. That is a special
``magic'' file name that refers to the controlling terminal of the
current process (if it has one). To find the name of the specific
Modified: fsf/trunk/libc/manual/lang.texi
==============================================================================
--- fsf/trunk/libc/manual/lang.texi (original)
+++ fsf/trunk/libc/manual/lang.texi Wed Feb 29 00:02:39 2012
@@ -454,7 +454,7 @@
@code{va_end} before returning from the function in which @code{va_start}
was invoked with the same @var{ap} argument.
-In the GNU C library, @code{va_end} does nothing, and you need not ever
+In @theglibc{}, @code{va_end} does nothing, and you need not ever
use it except for reasons of portability.
@refill
@end deftypefn
@@ -776,7 +776,7 @@
@item SHRT_MIN
This is the minimum value that can be represented by a @w{@code{signed
-short int}}. On most machines that the GNU C library runs on,
+short int}}. On most machines that @theglibc{} runs on,
@code{short} integers are 16-bit quantities.
@comment limits.h
@@ -795,7 +795,7 @@
@item INT_MIN
This is the minimum value that can be represented by a @w{@code{signed
-int}}. On most machines that the GNU C system runs on, an @code{int} is
+int}}. On most machines that @theglibc{} runs on, an @code{int} is
a 32-bit quantity.
@comment limits.h
@@ -813,7 +813,7 @@
@item LONG_MIN
This is the minimum value that can be represented by a @w{@code{signed
-long int}}. On most machines that the GNU C system runs on, @code{long}
+long int}}. On most machines that @theglibc{} runs on, @code{long}
integers are 32-bit quantities, the same size as @code{int}.
@comment limits.h
@@ -831,7 +831,7 @@
@item LLONG_MIN
This is the minimum value that can be represented by a @w{@code{signed
-long long int}}. On most machines that the GNU C system runs on,
+long long int}}. On most machines that @theglibc{} runs on,
@w{@code{long long}} integers are 64-bit quantities.
@comment limits.h
@@ -939,8 +939,8 @@
the exponent is @dfn{biased} by adding a constant to it, to make it
always be represented as an unsigned quantity. This is only important
if you have some reason to pick apart the bit fields making up the
-floating point number by hand, which is something for which the GNU
-library provides no support. So this is ignored in the discussion that
+floating point number by hand, which is something for which @theglibc{}
+provides no support. So this is ignored in the discussion that
follows.
@item
@@ -961,7 +961,7 @@
but not stored in memory because its value is always 1 in a normalized
number. The precision figure (see above) includes any hidden bits.
-Again, the GNU library provides no facilities for dealing with such
+Again, @theglibc{} provides no facilities for dealing with such
low-level aspects of the representation.
@end itemize
Modified: fsf/trunk/libc/manual/libc.texinfo
==============================================================================
--- fsf/trunk/libc/manual/libc.texinfo (original)
+++ fsf/trunk/libc/manual/libc.texinfo Wed Feb 29 00:02:39 2012
@@ -3,6 +3,8 @@
@setfilename libc.info
@settitle The GNU C Library
@c setchapternewpage odd
+
+@include macros.texi
@comment Tell install-info what to do.
@dircategory Software libraries
@@ -29,7 +31,7 @@
@set FDL_VERSION 1.3
@copying
-This file documents the GNU C library.
+This file documents @theglibc{}.
This is
@c Disabled (printed editions, see above).
@@ -94,7 +96,7 @@
@c Disabled (printed editions, see above).
@c Edition @value{EDITION} of
@cite{The GNU C Library Reference Manual}, for Version @value{VERSION}
-of the GNU C Library.
+of @theglibc{}.
@end ifnottex
@include top-menu.texi
Modified: fsf/trunk/libc/manual/llio.texi
==============================================================================
--- fsf/trunk/libc/manual/llio.texi (original)
+++ fsf/trunk/libc/manual/llio.texi Wed Feb 29 00:02:39 2012
@@ -332,7 +332,7 @@
reading any data, and reports this error.
@strong{Compatibility Note:} Most versions of BSD Unix use a different
-error code for this: @code{EWOULDBLOCK}. In the GNU library,
+error code for this: @code{EWOULDBLOCK}. In @theglibc{},
@code{EWOULDBLOCK} is an alias for @code{EAGAIN}, so it doesn't matter
which name you use.
@@ -483,7 +483,7 @@
character.
@strong{Compatibility Note:} Most versions of BSD Unix use a different
-error code for this: @code{EWOULDBLOCK}. In the GNU library,
+error code for this: @code{EWOULDBLOCK}. In @theglibc{},
@code{EWOULDBLOCK} is an alias for @code{EAGAIN}, so it doesn't matter
which name you use.
@@ -844,7 +844,7 @@
In some other systems, @code{fdopen} may fail to detect that the modes
for file descriptor do not permit the access specified by
-@code{opentype}. The GNU C library always checks for this.
+@code{opentype}. @Theglibc{} always checks for this.
@end deftypefun
For an example showing the use of the @code{fdopen} function,
@@ -1043,8 +1043,8 @@
because there is overhead associated with each kernel call.
Instead, many platforms provide special high-speed primitives to perform
-these @dfn{scatter-gather} operations in a single kernel call. The GNU C
-library will provide an emulation on any system that lacks these
+these @dfn{scatter-gather} operations in a single kernel call. @Theglibc{}
+will provide an emulation on any system that lacks these
primitives, so they are not a portability threat. They are defined in
@code{sys/uio.h}.
@@ -1216,7 +1216,7 @@
without creating a file.
On some systems using private anonymous mmaps is more efficient than using
-@code{malloc} for large blocks. This is not an issue with the GNU C library,
+@code{malloc} for large blocks. This is not an issue with @theglibc{},
as the included @code{malloc} automatically uses @code{mmap} where appropriate.
@c Linux has some other MAP_ options, which I have not discussed here.
@@ -2498,7 +2498,7 @@
implementation which uses threads for handling the enqueued requests.
While this implementation requires making some decisions about
limitations, hard limitations are something which is best avoided
-in the GNU C library. Therefore, the GNU C library provides a means
+in @theglibc{}. Therefore, @theglibc{} provides a means
for tuning the AIO implementation according to the individual use.
@comment aio.h
Modified: fsf/trunk/libc/manual/locale.texi
==============================================================================
--- fsf/trunk/libc/manual/locale.texi (original)
+++ fsf/trunk/libc/manual/locale.texi Wed Feb 29 00:02:39 2012
@@ -350,8 +350,8 @@
@end table
Defining and installing named locales is normally a responsibility of
-the system administrator at your site (or the person who installed the
-GNU C library). It is also possible for the user to create private
+the system administrator at your site (or the person who installed
+@theglibc{}). It is also possible for the user to create private
locales. All this will be discussed later when describing the tool to
do so.
@comment (@pxref{Building Locale Files}).
@@ -889,7 +889,7 @@
@item YESEXPR
The return value is a regular expression which can be used with the
@code{regex} function to recognize a positive response to a yes/no
-question. The GNU C library provides the @code{rpmatch} function for
+question. @Theglibc{} provides the @code{rpmatch} function for
easier handling in applications.
@item NOEXPR
The return value is a regular expression which can be used with the
@@ -1048,7 +1048,7 @@
number of fractional digits is selected to be zero, no decimal point is
printed.
-As a GNU extension, the @code{strfmon} implementation in the GNU libc
+As a GNU extension, the @code{strfmon} implementation in @theglibc{}
allows an optional @samp{L} next as a format modifier. If this modifier
is given, the argument is expected to be a @code{long double} instead of
a @code{double} value.
@@ -1179,7 +1179,7 @@
ask a question in one language and request the answer in another, often
English.
-The GNU C library contains @code{rpmatch} to give applications easy
+@Theglibc{} contains @code{rpmatch} to give applications easy
access to the corresponding locale definitions.
@comment GNU
@@ -1203,7 +1203,7 @@
regular expression.
@end table
-This function is not standardized but available beside in GNU libc at
+This function is not standardized but available beside in @theglibc{} at
least also in the IBM AIX library.
@end deftypefun
Added: fsf/trunk/libc/manual/macros.texi
==============================================================================
--- fsf/trunk/libc/manual/macros.texi (added)
+++ fsf/trunk/libc/manual/macros.texi Wed Feb 29 00:02:39 2012
@@ -1,0 +1,20 @@
+@c Define common macros used to keep phrasing consistent in the manual.
+
+@ifclear MACROS
+@set MACROS
+
+@c Names used to refer to the library, as noun phrases at the start or
+@c not at the start of a sentence.
+@macro Theglibc
+The GNU C Library
+@end macro
+@macro theglibc
+the GNU C Library
+@end macro
+
+@c Name used to refer to the library as an adjective.
+@macro glibcadj
+GNU C Library
+@end macro
+
+@end ifclear
Modified: fsf/trunk/libc/manual/maint.texi
==============================================================================
--- fsf/trunk/libc/manual/maint.texi (original)
+++ fsf/trunk/libc/manual/maint.texi Wed Feb 29 00:02:39 2012
@@ -4,8 +4,8 @@
@menu
* Source Layout:: How to add new functions or header files
- to the GNU C library.
-* Porting:: How to port the GNU C library to
+ to the GNU C Library.
+* Porting:: How to port the GNU C Library to
a new machine or operating system.
@end menu
@@ -105,9 +105,9 @@
@end table
@node Porting
-@appendixsec Porting the GNU C Library
-
-The GNU C library is written to be easily portable to a variety of
+@appendixsec Porting @theglibc{}
+
+@Theglibc{} is written to be easily portable to a variety of
machines and operating systems. Machine- and operating system-dependent
functions are well separated to make it easy to add implementations for
new machines or operating systems. This section describes the layout of
@@ -405,7 +405,7 @@
@end table
@node Porting to Unix
-@appendixsubsec Porting the GNU C Library to Unix Systems
+@appendixsubsec Porting @theglibc{} to Unix Systems
Most Unix systems are fundamentally very similar. There are variations
between different machines, and variations in what facilities are
@@ -452,10 +452,10 @@
@c It's not anymore true. glibc 2.1 cannot be used with K&R compilers.
@c --drepper
-Although the GNU C library implements the @w{ISO C} library facilities, you
-@emph{can} use the GNU C library with traditional, ``pre-ISO'' C
+Although @theglibc{} implements the @w{ISO C} library facilities, you
+@emph{can} use @theglibc{} with traditional, ``pre-ISO'' C
compilers. However, you need to be careful because the content and
-organization of the GNU C library header files differs from that of
+organization of the @glibcadj{} header files differs from that of
traditional C implementations. This means you may need to make changes
to your program in order to get it to compile.
@end ignore
Modified: fsf/trunk/libc/manual/math.texi
==============================================================================
--- fsf/trunk/libc/manual/math.texi (original)
+++ fsf/trunk/libc/manual/math.texi Wed Feb 29 00:02:39 2012
@@ -111,8 +111,8 @@
defined. The default set of features includes these constants.
@xref{Feature Test Macros}.
-All values are of type @code{double}. As an extension, the GNU C
-library also defines these constants with type @code{long double}. The
+All values are of type @code{double}. As an extension, @theglibc{}
+also defines these constants with type @code{long double}. The
@code{long double} macros have a lowercase @samp{l} appended to their
names: @code{M_El}, @code{M_PIl}, and so forth. These are only
available if @code{_GNU_SOURCE} is defined.
@@ -121,7 +121,7 @@
@emph{Note:} Some programs use a constant named @code{PI} which has the
same value as @code{M_PI}. This constant is not standard; it may have
appeared in some old AT&T headers, and is mentioned in Stroustrup's book
-on C++. It infringes on the user's name space, so the GNU C library
+on C++. It infringes on the user's name space, so @theglibc{}
does not define it. Fixing programs written to expect it is simple:
replace @code{PI} with @code{M_PI} throughout, or put @samp{-DPI=M_PI}
on the compiler command line.
@@ -217,7 +217,7 @@
@cindex complex trigonometric functions
@w{ISO C99} defines variants of the trig functions which work on
-complex numbers. The GNU C library provides these functions, but they
+complex numbers. @Theglibc{} provides these functions, but they
are only useful if your compiler supports the new complex types defined
by the standard.
@c XXX Change this when gcc is fixed. -zw
@@ -1275,7 +1275,7 @@
the same seed, used in different C libraries or on different CPU types,
will give you different random numbers.
-The GNU library supports the standard @w{ISO C} random number functions
+@Theglibc{} supports the standard @w{ISO C} random number functions
plus two other sets derived from BSD and SVID. The BSD and @w{ISO C}
functions provide identical, somewhat limited functionality. If only a
small number of random bits are required, we recommend you use the
@@ -1306,7 +1306,7 @@
@comment ISO
@deftypevr Macro int RAND_MAX
The value of this macro is an integer constant representing the largest
-value the @code{rand} function can return. In the GNU library, it is
+value the @code{rand} function can return. In @theglibc{}, it is
@code{2147483647}, which is the largest signed integer representable in
32 bits. In other libraries, it may be as low as @code{32767}.
@end deftypevr
@@ -1355,7 +1355,7 @@
This section describes a set of random number generation functions that
are derived from BSD. There is no advantage to using these functions
-with the GNU C library; we support them for BSD compatibility only.
+with @theglibc{}; we support them for BSD compatibility only.
The prototypes for these functions are in @file{stdlib.h}.
@pindex stdlib.h
@@ -1419,7 +1419,7 @@
hard to deal with situations where each thread should have its own
pseudo-random number generator.
-The GNU C library contains four additional functions which contain the
+@Theglibc{} contains four additional functions which contain the
state as an explicit parameter and therefore make it possible to handle
thread-local PRNGs. Beside this there is no difference. In fact, the
[... 2148 lines stripped ...]
_______________________________________________
Commits mailing list
Commits@xxxxxxxxxx
http://eglibc.org/cgi-bin/mailman/listinfo/commits