mirror of
git://git.sv.gnu.org/autoconf
synced 2025-03-31 15:00:26 +08:00
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. Signed-off-by: Eric Blake <eblake@redhat.com>
This commit is contained in:
parent
a90f3e25cc
commit
d847c5d01b
@ -1,3 +1,11 @@
|
||||
2010-07-19 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
|
||||
|
||||
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.
|
||||
|
||||
2010-07-10 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
|
||||
|
||||
Fix comment typo in the manual.
|
||||
|
@ -2432,9 +2432,9 @@ when you call @code{AC_PROG_CC} (or empty if you don't). @command{configure}
|
||||
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
|
||||
@var{directory}}), it should be put into @code{LDFLAGS} instead. If it
|
||||
(e.g., @option{-D@var{name}}), it should be put into @code{CPPFLAGS}
|
||||
instead. If it affects only the linker (e.g., @option{-L@var{directory}}),
|
||||
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
|
||||
|
Loading…
x
Reference in New Issue
Block a user