[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
manual: compiler flags -D and -L should not be followed by space.
From: |
Ralf Wildenhues |
Subject: |
manual: compiler flags -D and -L should not be followed by space. |
Date: |
Sun, 11 Jul 2010 12:12:57 +0200 |
User-agent: |
Mutt/1.5.20 (2010-04-22) |
Any reasons against committing this nearly-obvious patch?
Thanks,
Ralf
manual: compiler flags -D and -L should not be followed by space.
* doc/autoconf.texi (Preset Output Variables): Remove space
between -D and -L flags and their arguments, traditional cpp
implementations like Solaris 10, IRIX 6.5, OSF Tru64 5.1D,
AIX 5.3 do not accept it.
diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index fc247a4..bf434eb 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -2432,9 +2432,9 @@ Preset Output Variables
uses this variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
-(e.g., @option{-D @var{name}}), it should be put into @code{CPPFLAGS}
-instead. If it affects only the linker (e.g., @option{-L
address@hidden), it should be put into @code{LDFLAGS} instead. If it
+(e.g., @address@hidden), it should be put into @code{CPPFLAGS}
+instead. If it affects only the linker (e.g., @address@hidden),
+it should be put into @code{LDFLAGS} instead. If it
affects only the compiler proper, @code{CFLAGS} is the natural home for
it. If an option affects multiple phases of the compiler, though,
matters get tricky. One approach to put such options directly into
- manual: compiler flags -D and -L should not be followed by space.,
Ralf Wildenhues <=