[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AM_CFLAGS no longer in the manual

From: Jeffrey Walton
Subject: Re: AM_CFLAGS no longer in the manual
Date: Sun, 9 Dec 2012 17:06:10 -0500

On Sun, Dec 9, 2012 at 3:44 PM, Diego Elio Pettenò
<address@hidden> wrote:
> On 09/12/2012 17:32, NightStrike wrote:
>> It's not more fully documented elsewhere, though.  AM_CPPFLAGS right
>> about it is, however, fully documented right in this section.  This
>> should be fixed, since nowhere does the manual say that AM_CFLAGS is
>> "-g -O2" by default.
> Is it? I was confident that AM_CFLAGS is unset by default, but CFLAGS
> (from autoconf) is "-g -O2" by default.
> And no you shouldn't change CFLAGS in, please. That's an
> user-assignable variable, distributions cry every time that we have to
> patch a CFLAGS="$something" in Especially when that's to
> set/unset -O and -g flags depending on a debug/release build (hint:
> distributions want debug information with optimized builds as well!).
Seems reasonable (otherwise a stack trace is useless). Also, it does
not affect performance. Confer: "How does the gcc -g option affect


reply via email to

[Prev in Thread] Current Thread [Next in Thread]