Ralf Wildenhues wrote:
> * standards.texi (Configuration): Document that `configure'
> should accept arguments of the form `VARIABLE=VALUE' and why
> they are preferable over environment variables.
> Suggested by Bruno Haible.
Looks quite good. Just two proposed further changes:
--- standards.texi.rw 2006-08-10 14:03:50.000000000 +0200
+++ standards.texi.rw.bh 2006-08-10 14:08:28.000000000 +0200
@@ -3761,9 +3761,8 @@
@cindex optional features, configure-time
Other options are permitted to specify in more detail the software
-or hardware present on the machine, adjust the name of some tools
-or arguments to them, and include or exclude optional parts of the
-package:
+or hardware present on the machine, to include or exclude optional parts
+of the package, or to adjust the name of some tools or arguments to them:
@table @samp
@item --enable-@var{feature}@r{[}=@var{parameter}@r{]}
@@ -3801,7 +3800,9 @@
Set the value of the variable @var{variable} to @var{value}. This may
be used to override some commands or arguments to values differing from
the ones the build process would use otherwise. For example, the user
-could issue @samp{configure CFLAGS=-g} to build with debugging symbols.
+could issue @samp{configure CFLAGS=-g CXXFLAGS=-g} to build with
+debugging information and without the default optimization.
+
Specifying variables as arguments to @code{configure}:
@example
./configure CC=gcc
The first one is to mention the options in the same order as they
appear in the table (otherwise it can be confusing).
The second one is because
- -g not only adds symbols, but also line number information to an
executable,
- CFLAGS=-g will have no effect if you happen to be compiling a C++
program,
- the default CFLAGS (when using gcc) being "-g -O2", one of the effects
of CFLAGS=-g is to disable the optimisations which make debugging a
big pain.
Bruno
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
