Follow-up Comment #1, bug #56420 (project make):
The context, specifically the start of the previous paragraph:
> If there are C compiler options that _must_ be used for proper compilation
of certain files, do not include them in CFLAGS.
...
> Do include the ‘-g’ option in CFLAGS, because that is not _required_ for
proper compilation.
... tells us that the OP is wrong to think, if they do, that "Don't" was
intended. Perhaps this would make the contrast clearer:
martind@swiftboat:~/download/make-git/gnulib/doc$ git diff
diff --git a/doc/make-stds.texi b/doc/make-stds.texi
index d37b244..c390ffe 100644
--- a/doc/make-stds.texi
+++ b/doc/make-stds.texi
@@ -254,7 +254,7 @@ ALL_CFLAGS = -I. $(CFLAGS)
$(CC) -c $(CPPFLAGS) $(ALL_CFLAGS) $<
@end smallexample
-Do include the @samp{-g} option in @code{CFLAGS}, because that is not
+Do, however, include the @samp{-g} option in @code{CFLAGS}, because that is
not
@emph{required} for proper compilation. You can consider it a default
that is only recommended. If the package is set up so that it is
compiled with GCC by default, then you might as well include @samp{-O}
martind@swiftboat:~/download/make-git/gnulib/doc$
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?56420>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
