This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Clean up glibc version numbers in manual


I've committed this patch in the following form (which also updates the 
copyright notice in libc.texinfo and makes it use @copyright{} for the 
copyright symbol and a range for the years).  So far as there were 
comments they just seemed to be suggesting *other* old versions to clean 
up, not objecting to this part of the cleanup - and as each cleanup is 
likely to affect text also affected by other cleanups, it seems a good 
idea to get such cleanups in quickly.

Incidental observation: the preexisting use of @copying means that at 
least Texinfo 4.2 is in fact required for the manual (not 4.0 as accepted 
by the configure script, or 3.12f as indicated in install.texi).

diff --git a/ChangeLog b/ChangeLog
index 5ea30b9..366d891 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,12 @@
 2012-02-21  Joseph Myers  <joseph@codesourcery.com>
 
+	* manual/install.texi: Do not mention specific glibc version
+	numbers.
+	* manual/libc.texinfo (VERSION, UPDATED): Update.
+	(@copying): Use @copyright{} and range of years.
+
+2012-02-21  Joseph Myers  <joseph@codesourcery.com>
+
 	[BZ #13695]
 	* csu/Makefile (distribute): Remove initfini.c and defs.awk.
 	[crti.S not in sysdirs] (generated): Do not append.
diff --git a/manual/install.texi b/manual/install.texi
index 61ff23c..8bfd5f1 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -35,7 +35,7 @@ GNU Make, and possibly others.  @xref{Tools for Compilation}, below.
 
 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 @file{/src/gnu/glibc-2.4}, create a directory
+the glibc 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.
@@ -44,7 +44,7 @@ From your object directory, run the shell script @file{configure} located
 at the top level of the source tree.  In the scenario above, you'd type
 
 @smallexample
-$ ../glibc-2.4/configure @var{args@dots{}}
+$ ../glibc-@var{version}/configure @var{args@dots{}}
 @end smallexample
 
 Please note that even though you're building in a separate build
@@ -98,7 +98,7 @@ spaces or commas (if you use spaces, remember to quote them from the
 shell).  Each add-on in @var{list} can be an absolute directory name
 or can be a directory name relative to the main source directory, or
 relative to the build directory (that is, the current working directory).
-For example, @samp{--enable-add-ons=nptl,../glibc-libidn-2.4}.
+For example, @samp{--enable-add-ons=nptl,../glibc-libidn-@var{version}}.
 
 @item --enable-kernel=@var{version}
 This option is currently only useful on GNU/Linux systems.  The
@@ -262,7 +262,7 @@ 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 2.2 includes a daemon called @code{nscd}, which you
+Glibc 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.
@@ -315,11 +315,11 @@ bugs or lack features.
 @item
 GCC 3.4 or newer, GCC 4.1 recommended
 
-For the 2.4 release or later, GCC 3.4 or higher is required; as of this
+GCC 3.4 or higher is required; as of this
 writing, GCC 4.4 is the compiler we advise to use for current versions.
 On certain machines including @code{powerpc64}, compilers prior to GCC
-4.0 have bugs that prevent them compiling the C library code in the
-2.4 release.  On other machines, GCC 4.1 is required to build the C
+4.0 have bugs that prevent them compiling the C library code.  On other
+machines, GCC 4.1 is required to build the C
 library with support for the correct @code{long double} type format;
 these include @code{powerpc} (32 bit), @code{s390} and @code{s390x}.  For
 other architectures special compiler-provided headers are needed
diff --git a/manual/libc.texinfo b/manual/libc.texinfo
index dfbfac3..0ac764f 100644
--- a/manual/libc.texinfo
+++ b/manual/libc.texinfo
@@ -19,8 +19,8 @@
 
 @c sold 0.06/1.09, print run out 21may96
 @set EDITION 0.13
-@set VERSION 2.14
-@set UPDATED 2011-07-19
+@set VERSION 2.15.90
+@set UPDATED 2012-02-21
 @set ISBN 1-882114-55-8
 
 @copying
@@ -29,8 +29,7 @@ This file documents the GNU C library.
 This is Edition @value{EDITION}, last updated @value{UPDATED},
 of @cite{The GNU C Library Reference Manual}, for version @value{VERSION}.
 
-Copyright (C) 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2001, 2002,
-2003, 2007, 2008, 2010, 2011 Free Software Foundation, Inc.
+Copyright @copyright{} 1993--2012 Free Software Foundation, Inc.
 
 Permission is granted to copy, distribute and/or modify this document
 under the terms of the GNU Free Documentation License, Version 1.3 or

-- 
Joseph S. Myers
joseph@codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]