Re: grep 2.5: CFLAGS

[Karl Berry]

    Doing it the right way(tm) works:

Thanks.  I actually knew that, but as Miles said, that's not the point.
The point is that GNU standards say CFLAGS should be reserved for the
user, not used for required compiler options.  Therefore it's a bug.  So
can it please be fixed?


    CFLAGS="-g" ./configure --whatever

Incidentally, I think configure recommends configure CFLAGS=-g now.  I
don't know why, seems like more gratuitious incompatibility on the face
of it, but I'm sure Akim and crew had a very good reason.  ("customized
values may be lost"?  Why?)

Thanks,
karl


File: autoconf.info,  Node: Defining Variables

Defining Variables
==================

   Variables not defined in a site shell script can be set in the
environment passed to `configure'.  However, some packages may run
configure again during the build, and the customized values of these
variables may be lost.  In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'.  For example:

     ./configure CC=/usr/local2/bin/gcc

will cause the specified gcc to be used as the C compiler (unless it is
overridden in the site shell script).