Permalink
Browse files

* Makefile (format-me): Use --plaintext --no-number-sections.

	* NOTES, INSTALL: Regenerated.
  • Loading branch information...
1 parent 35129bc commit c9dc3f62698e9b456869ba8c1f0fd8f3c672ebf2 Roland McGrath committed Mar 1, 2006
Showing with 45 additions and 46 deletions.
  1. +3 −0 ChangeLog
  2. +14 −14 INSTALL
  3. +1 −1 Makefile
  4. +27 −31 NOTES
View
3 ChangeLog
@@ -1,5 +1,8 @@
2006-03-01 Roland McGrath <roland@redhat.com>
+ * Makefile (format-me): Use --plaintext --no-number-sections.
+ * NOTES, INSTALL: Regenerated.
+
* NEWS: Update 2.4 items.
2006-03-01 David S. Miller <davem@sunset.davemloft.net>
View
28 INSTALL
@@ -1,5 +1,5 @@
-Appendix A Installing the GNU C Library
-***************************************
+Installing the GNU C Library
+****************************
Before you do anything else, you should read the file `FAQ' located at
the top level of the source tree. This file answers common questions
@@ -15,8 +15,8 @@ activate them, and they will be compiled into the library.
and GNU Make, and possibly others. *Note Tools for Compilation::,
below.
-A.1 Configuring and compiling GNU Libc
-======================================
+Configuring and compiling GNU Libc
+==================================
GNU libc can be compiled in the source directory, but we strongly advise
building it in a separate build directory. For example, if you have
@@ -205,8 +205,8 @@ library. You may need to set `AR' and `RANLIB' to cross-compiling
versions of `ar' and `ranlib' if the native tools are not configured to
work with object files for the target you configured for.
-A.2 Installing the C Library
-============================
+Installing the C Library
+========================
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
@@ -279,8 +279,8 @@ which is in `/usr/share/zoneinfo' to the file `/etc/localtime'. For
Germany, you might execute `ln -s /usr/share/zoneinfo/Europe/Berlin
/etc/localtime'.
-A.3 Recommended Tools for Compilation
-=====================================
+Recommended Tools for Compilation
+=================================
We recommend installing the following GNU tools before attempting to
build the GNU C library:
@@ -359,8 +359,8 @@ and if you change any of the message translation files you will need
You may also need these packages if you upgrade your source tree using
patches, although we try to avoid this.
-A.4 Supported Configurations
-============================
+Supported Configurations
+========================
The GNU C Library currently supports configurations that match the
following patterns:
@@ -431,8 +431,8 @@ some `i686' specific instructions. To generate code for other models,
you have to configure for that model and give GCC the appropriate
`-march=' and `-mcpu=' compiler switches via CFLAGS.
-A.5 Specific advice for GNU/Linux systems
-=========================================
+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.2 or newer kernel around for reference. For
@@ -486,8 +486,8 @@ kernel-side thread support. `nscd' happens to hit these bugs
particularly hard, but you might have problems with any threaded
program.
-A.6 Reporting Bugs
-==================
+Reporting Bugs
+==============
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
View
2 Makefile
@@ -399,7 +399,7 @@ tag-%: $(files-for-dist)
define format-me
@rm -f $@
-makeinfo --no-validate --no-warn --no-headers $< -o $@
+makeinfo --no-validate --plaintext --no-number-sections $< -o $@
-chmod a-w $@
endef
INSTALL: manual/install.texi; $(format-me)
View
58 NOTES
@@ -1,8 +1,8 @@
Feature Test Macros
-------------------
- The exact set of features available when you compile a source file
-is controlled by which "feature test macros" you define.
+The exact set of features available when you compile a source file is
+controlled by which "feature test macros" you define.
If you compile your programs using `gcc -ansi', you get only the
ISO C library features, unless you explicitly request additional
@@ -32,15 +32,15 @@ limited standard. It is insufficient for this purpose, as it will not
protect you from including header files outside the standard, or
relying on semantics undefined within the standard.
- - Macro: _POSIX_SOURCE
+ -- Macro: _POSIX_SOURCE
If you define this macro, then the functionality from the POSIX.1
standard (IEEE Standard 1003.1) is available, as well as all of the
ISO C facilities.
The state of `_POSIX_SOURCE' is irrelevant if you define the macro
`_POSIX_C_SOURCE' to a positive integer.
- - Macro: _POSIX_C_SOURCE
+ -- Macro: _POSIX_C_SOURCE
Define this macro to a positive integer to control which POSIX
functionality is made available. The greater the value of this
macro, the more functionality is made available.
@@ -65,12 +65,7 @@ relying on semantics undefined within the standard.
greater than or equal to `199506L', then the functionality from
the 1996 edition is made available.
- The Single Unix Specification specify that setting this macro to
- the value `199506L' selects all the values specified by the POSIX
- standards plus those of the Single Unix Specification, i.e., is the
- same as if `_XOPEN_SOURCE' is set to `500' (see below).
-
- - Macro: _BSD_SOURCE
+ -- Macro: _BSD_SOURCE
If you define this macro, functionality derived from 4.3 BSD Unix
is included as well as the ISO C, POSIX.1, and POSIX.2 material.
@@ -88,15 +83,15 @@ relying on semantics undefined within the standard.
must give the option `-lbsd-compat' to the compiler or linker when
linking the program, to tell it to find functions in this special
compatibility library before looking for them in the normal C
- library.
+ library.
- - Macro: _SVID_SOURCE
+ -- Macro: _SVID_SOURCE
If you define this macro, functionality derived from SVID is
included as well as the ISO C, POSIX.1, POSIX.2, and X/Open
material.
- - Macro: _XOPEN_SOURCE
- - Macro: _XOPEN_SOURCE_EXTENDED
+ -- Macro: _XOPEN_SOURCE
+ -- Macro: _XOPEN_SOURCE_EXTENDED
If you define this macro, functionality described in the X/Open
Portability Guide is included. This is a superset of the POSIX.1
and POSIX.2 functionality and in fact `_POSIX_SOURCE' and
@@ -113,19 +108,19 @@ relying on semantics undefined within the standard.
functionality described so far plus some new definitions from the
Single Unix Specification, version 2.
- - Macro: _LARGEFILE_SOURCE
+ -- Macro: _LARGEFILE_SOURCE
If this macro is defined some extra functions are available which
- rectify a few shortcomings in all previous standards. More
- concrete the functions `fseeko' and `ftello' are available.
+ rectify a few shortcomings in all previous standards.
+ Specifically, the functions `fseeko' and `ftello' are available.
Without these functions the difference between the ISO C interface
(`fseek', `ftell') and the low-level POSIX interface (`lseek')
would lead to problems.
This macro was introduced as part of the Large File Support
extension (LFS).
- - Macro: _LARGEFILE64_SOURCE
- If you define this macro an additional set of function is made
+ -- Macro: _LARGEFILE64_SOURCE
+ If you define this macro an additional set of functions is made
available which enables 32 bit systems to use files of sizes beyond
the usual limit of 2GB. This interface is not available if the
system does not support files that large. On systems where the
@@ -138,13 +133,13 @@ relying on semantics undefined within the standard.
`off64_t' and `fseeko' vs. `fseeko64'.
This macro was introduced as part of the Large File Support
- extension (LFS). It is a transition interface for the time 64 bit
- offsets are not generally used (see `_FILE_OFFSET_BITS'.
+ extension (LFS). It is a transition interface for the period when
+ 64 bit offsets are not generally used (see `_FILE_OFFSET_BITS').
- - Macro: _FILE_OFFSET_BITS
+ -- Macro: _FILE_OFFSET_BITS
This macro determines which file system interface shall be used,
- one replacing the other. While `_LARGEFILE64_SOURCE' makes the
- 64 bit interface available as an additional interface
+ one replacing the other. Whereas `_LARGEFILE64_SOURCE' makes the
+ 64 bit interface available as an additional interface,
`_FILE_OFFSET_BITS' allows the 64 bit interface to replace the old
interface.
@@ -154,9 +149,10 @@ relying on semantics undefined within the standard.
If the macro is defined to the value `64', the large file interface
replaces the old interface. I.e., the functions are not made
- available under different names as `_LARGEFILE64_SOURCE' does.
- Instead the old function names now reference the new functions,
- e.g., a call to `fseeko' now indeed calls `fseeko64'.
+ available under different names (as they are with
+ `_LARGEFILE64_SOURCE'). Instead the old function names now
+ reference the new functions, e.g., a call to `fseeko' now indeed
+ calls `fseeko64'.
This macro should only be selected if the system provides
mechanisms for handling large files. On 64 bit systems this macro
@@ -166,13 +162,13 @@ relying on semantics undefined within the standard.
This macro was introduced as part of the Large File Support
extension (LFS).
- - Macro: _ISOC99_SOURCE
+ -- 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.
- - Macro: _GNU_SOURCE
+ -- Macro: _GNU_SOURCE
If you define this macro, everything is included: ISO C89,
ISO C99, POSIX.1, POSIX.2, BSD, SVID, X/Open, LFS, and GNU
extensions. In the cases where POSIX.1 conflicts with BSD, the
@@ -191,8 +187,8 @@ relying on semantics undefined within the standard.
compiler or linker. *Note:* If you forget to do this, you may get
very strange errors at run time.
- - Macro: _REENTRANT
- - Macro: _THREAD_SAFE
+ -- Macro: _REENTRANT
+ -- 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

0 comments on commit c9dc3f6

Please sign in to comment.