According to Eric Blake on 2/25/2010 2:57 PM:
> 2 weeks turned into 7 months.  Sorry for not replying to this thread
> sooner.  I like Paolo's suggestion of documenting that it is acceptable to
> change the default CXXFLAGS if the package author doesn't like autoconf's
> default, without penalizing the user's ability to specify better arguments
> than the package default.  How does this wording look?

Of course, this needs to be squashed in, to avoid texinfo errors.

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index 3bb2e42..191a397 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -7150,7 +7150,7 @@ C Compiler
 it to @option{-g -O2} for the @acronym{GNU} C compiler (@option{-O2} on
systems
 where @acronym{GCC} does not accept @option{-g}), or @option{-g} for
 other compilers.  If your package does not like this default, then it is
-acceptable to insert the line @samp{: ${CFLAGS=""}} after @code{AC_INIT}
+acceptable to insert the line @samp{: $...@{cflags=""@}} after @code{AC_INIT}
 and before @code{AC_PROG_CC} to select an empty default instead.

 Many Autoconf macros use a compiler, and thus call
@@ -7553,7 +7553,7 @@ C++ Compiler
 it to @option{-g -O2} for the @acronym{GNU} C++ compiler (@option{-O2} on
 systems where G++ does not accept @option{-g}), or @option{-g} for other
 compilers.  If your package does not like this default, then it is
-acceptable to insert the line @samp{: ${CXXFLAGS=""}} after @code{AC_INIT}
+acceptable to insert the line @samp{: $...@{cxxflags=""@}} after @code{AC_INIT}
 and before @code{AC_PROG_CXX} to select an empty default instead.

 @end defmac

-- 
Eric Blake   [email protected]    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to