Default CFLAGS clobbering

[Michael Nottebrock]

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.

> And KDE does so, too (it 
> doesn't inherit that default through AC_PROG_CC though) .

Which is too bad because if it did it would DTRT.

> So the behaviour of is consistent for users (among a large pool of
> software)

On the contrary, KDE's benevolent forcing of optimization flags is pretty 
extraordinary and should cease.

-- 
   ,_,   | 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/272ecfc6/attachment.sig>