From 3d26a952f2b50aca82e0728110286fc302206cec Mon Sep 17 00:00:00 2001 From: Christos Kontas Date: Sat, 23 Jan 2010 23:23:08 +0200 Subject: [PATCH] Fix some typos in the manual --- doc/automake.texi | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/automake.texi b/doc/automake.texi index d421e0b..1632dcd 100644 --- a/doc/automake.texi +++ b/doc/automake.texi @@ -1305,7 +1305,7 @@ run the @command{configure} script of B as part of its execution, building and installing A will also build and install B. Generating a distribution for A will also include B. -It is possible to gather several package like this. GCC is a heavy +It is possible to gather several packages like this. GCC is a heavy user of this feature. This gives installers a single package to configure, build and install, while it allows developers to work on subpackages independently. @@ -8856,7 +8856,7 @@ Sometimes it is convenient to supplement the rebuild rules for @file{configure} or @file{config.status} with additional dependencies. The variables @code{CONFIGURE_DEPENDENCIES} and @code{CONFIG_STATUS_DEPENDENCIES} can be used to list these extra -dependencies. These variable should be defined in all +dependencies. These variables should be defined in all @file{Makefile}s of the tree (because these two rebuild rules are output in all them), so it is safer and easier to @code{AC_SUBST} them from @file{configure.ac}. For instance, the following statement will -- 1.5.4.3