From: Richard M. Stallman <rms@gnu.org>
Date: Sat, 17 May 1997 19:07:42 +0000 (+0000)
Subject: Explain which commands should use CFLAGS.
X-Git-Tag: fsf-origin~52
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=118b55b292398276819b7e07d4889fa8fc2a3e3b;p=thirdparty%2Fautoconf.git

Explain which commands should use CFLAGS.
---

diff --git a/doc/make-stds.texi b/doc/make-stds.texi
index e7c9cf982..3f4b4ca69 100644
--- a/doc/make-stds.texi
+++ b/doc/make-stds.texi
@@ -239,6 +239,9 @@ Put @code{CFLAGS} last in the compilation command, after other variables
 containing compiler options, so the user can use @code{CFLAGS} to
 override the others.
 
+@code{CFLAGS} should be used in every invocation of the C compiler,
+both those which do compilation and those which do linking.
+
 Every Makefile should define the variable @code{INSTALL}, which is the
 basic command for installing a file into the system.
 
diff --git a/make-stds.texi b/make-stds.texi
index e7c9cf982..3f4b4ca69 100644
--- a/make-stds.texi
+++ b/make-stds.texi
@@ -239,6 +239,9 @@ Put @code{CFLAGS} last in the compilation command, after other variables
 containing compiler options, so the user can use @code{CFLAGS} to
 override the others.
 
+@code{CFLAGS} should be used in every invocation of the C compiler,
+both those which do compilation and those which do linking.
+
 Every Makefile should define the variable @code{INSTALL}, which is the
 basic command for installing a file into the system.