On 3/4/07, Dennis Schridde <[EMAIL PROTECTED]> wrote:
> If ${WZ_FLAGS} are to be able to override the default flags
> (for example, -O2), it has to be *after* ${CFLAGS} when we
> sum up compiler flags. Otherwise the setting of some flags
>
> >from within configure will be rather pointless.
I did that change on purpose...
If you do it like this, the user has no possibility to override eg. the
optimization flags. And some users might depend on that possibility.
Well, as long as we have a --enable-debug=N mode that attempts to set
optimization flags, you cannot do it that way. If you want to remove
the setting of optimization flags from this option, then fine. But
don't just break the debug option and leave it broken...
It matters because I try to keep "strict" working, and -Werror
generates additional problems with -O2 that are not shown with -O0.
The problem is that CFLAGS is set to "-g -O2" by default. I know of no
way of finding out whether this is the default value or a user given
value.
- Per
_______________________________________________
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev
