Default CFLAGS clobbering

[Michael Nottebrock]

On Saturday 22 May 2004 18:43, Simon Hausmann wrote:
> On Saturday 22 May 2004 18:28, Michael Nottebrock wrote:
> > On Saturday 22 May 2004 17:17, Simon Hausmann wrote:
> > > This is autoconf's default when using gcc (per c.m4) , so the whole
> > > pool of autoconf'ed software out there behaves that way.
> >
> > Uhm, you must be reading it wrong. AC_PROG_CC generates a check that sets
> > -g -O2 if CFLAGS is not specified _at all_ (and gcc is used), if CFLAGS
> > are specified it uses them verbatim without any additions.
>
> True, I misread that. But then we should behave like that, too, and not
> simply get rid of the -O2 in the default CFLAGS as suggested originally.

That would be perfectly fine with me, so let me rephrase my request: Can we 
please stop prepending -O2 to existing C(XX)FLAGS? I don't care about the 
debug-enabled cases.

-- 
   ,_,   | Michael Nottebrock               | lofi at freebsd.org
 (/^ ^\) | FreeBSD - The Power to Serve     | http://www.freebsd.org
   \u/   | K Desktop Environment on FreeBSD | http://freebsd.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: signature
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20040522/1fa64480/attachment.sig>