Update.

1999-04-03  Andreas Jaeger  <aj@arthur.rhein-neckar.de>

	* manual/install.texi (Configuring and compiling): Explain that
	files are changed in the source directory.
	Closes PR libc/981.
	(Configuring and compiling): Explain situation with PARALLELMFLAGS
	in the source directory.

1999-04-24  Andreas Schwab  <schwab@issan.cs.uni-dortmund.de>

	* locale/programs/ld-ctype.c: Spelling fixes.
	(ctype_finish): Fix argument of error message format.
	* locale/programs/ld-messages.c: Spelling fixes.
	* locale/programs/ld-monetary.c: Spelling fixes.
	* locale/programs/ld-time.c (time_finish): Make sure that name and
	format of era_entries are adjacent.
	(time_output): Reduce the size of the io vector.

1999-04-25  Andreas Schwab  <schwab@issan.cs.uni-dortmund.de>

	* manual/filesys.texi (Attribute Meanings): Move a misplaced
	paragraph.

1999-04-23  Andreas Schwab  <schwab@issan.cs.uni-dortmund.de>

	* locale/programs/ld-collate.c (collate_output): Convert
	undefined_offset to an array index.  Fix computation of other
	endian extra table.

1 files changed, 9 insertions, 1 deletions

diff --git a/manual/install.texi b/manual/install.texi
index c62c3481f4..ec00c01489 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -60,6 +60,10 @@ at the top level of the source tree.  In the scenario above, you'd type
 $ ../glibc-2.1.0/configure @var{args...}
 @end smallexample
 
+Please note that even if you're building in a separate build directory,
+the compiliation needs to modify a few files in the source
+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
@@ -193,7 +197,11 @@ Instead, edit the generated @file{Makefile} and uncomment the line
 
 @noindent
 You can change the @samp{4} to some other number as appropriate for
-your system.
+your system.  Instead of changing the @file{Makefile}, you could give
+this option directly to @code{make} and call it as, e.g. 
+@code{make PARALLELMFLAGS=-j4}.  If you're building in the source
+directory, you've got to use the latter approach since in this case no
+new @file{Makefile} is generated which you can change.
 
 To build and run some test programs which exercise some of the library
 facilities, type @code{make check}.  This should complete successfully;