Re: configure sets CFLAGS or how to disable default CFLAGS='-g -O2' for gcc?

[Ralf Wildenhues]

* Chris Pickett wrote on Wed, Apr 05, 2006 at 07:28:23AM CEST:
> For example, I didn't know AC_PROG_CC set "-g -O2", even 
> though I had been using it for a while.

Quoting info Autoconf "C Compiler":
|  If using the GNU C compiler, set shell variable `GCC' to `yes'.
|  If output variable `CFLAGS' was not already set, set it to `-g
|  -O2' for the GNU C compiler (`-O2' on systems where GCC does not
|  accept `-g'), or `-g' for other compilers.


> So, how about providing special flags for known platforms, and a safe 
> default for unknown platforms?  Add to this protection by configure 
> options so the user really has to want my flags to get them.  Is this an 
> acceptable compromise?

In general, overridability is more important than the special-casing.

Cheers,
Ralf