Ralf Wildenhues wrote:
* 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.
I know that now, of course. What I meant was that I don't always read
or perhaps more importantly remember the full documentation for every
single command I use, especially when they appear to be working just
fine. It was in response to Jacob's, "presumably, if you are adding
stuff, you already know exactly why you are adding it, exactly what it
does, and exactly what the consequences are." That's all. I'm a human
catastrophe.
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.
Okay.
I realize this whole discussion might be (is!) getting annoying, so I'll
try to be quiet again.
Cheers,
Chris
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
