about summary refs log tree commit diff
path: root/manual/install.texi
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>2002-06-30 04:04:20 +0000
committerUlrich Drepper <drepper@redhat.com>2002-06-30 04:04:20 +0000
commit95fdc6a0f61a389e92a6b84250c2286b4808b626 (patch)
tree54afe4d2de7ab4aeb9a6d0943ab90d8ddc794c0a /manual/install.texi
parent8b8cc76fa47fe0819e5e52e29c6674e799df646e (diff)
downloadglibc-95fdc6a0f61a389e92a6b84250c2286b4808b626.tar.gz
glibc-95fdc6a0f61a389e92a6b84250c2286b4808b626.tar.xz
glibc-95fdc6a0f61a389e92a6b84250c2286b4808b626.zip
Update.
2002-06-19  Steven Munroe  <sjmunroe@vnet.ibm.com>

	* Examples/ex9.c (main):  Use list of children and join them.
	(thread): Do not call exit.
Diffstat (limited to 'manual/install.texi')
-rw-r--r--manual/install.texi8
1 files changed, 4 insertions, 4 deletions
diff --git a/manual/install.texi b/manual/install.texi
index afadcdbc10..a8f003d81a 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -45,7 +45,7 @@ GNU Make, and possibly others.  @xref{Tools for Compilation}, below.
 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
  unpacked
-the glibc sources in @file{/src/gnu/glibc-2.2.0}, create a directory
+the glibc sources in @file{/src/gnu/glibc-2.3}, 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 +54,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.2.0/configure @var{args...}
+$ ../glibc-2.3/configure @var{args@dots{}}
 @end smallexample
 
 Please note that even if you're building in a separate build directory,
@@ -64,9 +64,9 @@ directory, especially some files in the manual subdirectory.
 @noindent
 @code{configure} takes many options, but you can get away with knowing
 only two: @samp{--prefix} and @samp{--enable-add-ons}.  The
-@code{--prefix} option tells @code{configure} where you want glibc 
+@code{--prefix} option tells @code{configure} where you want glibc
 installed. This defaults to @file{/usr/local}.  The
-@samp{--enable-add-ons} option tells @code{configure} to use all the 
+@samp{--enable-add-ons} option tells @code{configure} to use all the
 add-on bundles it finds in the source directory.  Since important
 functionality is provided in add-ons, you should always specify this
 option.