+2008-08-19 Reuben Thomas <rrt@sc3d.org> (tiny patch)
+
+ * doc/automake.texi (Flag Variables Ordering, Per-Object Flags):
+ Fix grammaros.
+
2008-08-02 Karl Berry <karl@freefriends.org>
* lib/gnupload: Provide also a simple example.
(@pxref{Tags}) use @code{ETAGSFLAGS}, @code{AM_ETAGSFLAGS},
@code{CTAGSFLAGS}, and @code{AM_CTAGSFLAGS}. Java rules
(@pxref{Java}) use @code{JAVACFLAGS} and @code{AM_JAVACFLAGS}. None
-of these rules do support per-target flags (yet).
+of these rules supports per-target flags (yet).
To some extent, even @code{AM_MAKEFLAGS} (@pxref{Subdirectories})
obeys this naming scheme. The slight difference is that
@file{foo.c} or @file{foo-foo.o} specifically.
What if @file{foo.c} needs to be compiled into @file{foo.o} using some
-specific flags, that none of the other files require? Obviously
+specific flags, that none of the other files requires? Obviously
per-program flags are not directly applicable here. Something like
per-object flags are expected, i.e., flags that would be used only
when creating @file{foo-foo.o}. Automake does not support that,