Sérgio Durigan Júnior [EMAIL PROTECTED] writes:
My question is about the CFLAGS variable. What should be the standard
behaviour when I provide my own CFLAGS (in this case, '-m64') for
configure script? Should it override its own CFLAGS and use only mine,
or should it append my CFLAGS to its
Hi Andreas,
On Wed, 2008-04-16 at 16:57 +0200, Andreas Schwab wrote:
Sérgio Durigan Júnior [EMAIL PROTECTED] writes:
My question is about the CFLAGS variable. What should be the standard
behaviour when I provide my own CFLAGS (in this case, '-m64') for
configure script? Should it
On Wed, 16 Apr 2008, Sérgio Durigan Júnior wrote:
In general a configure script should never modify CFLAGS. But flags
like -m64 that select a completely different ABI should better be put in
CC, not CFLAGS.
I will second the above statement.
Does that mean that CFLAGS is a variable only for
On Wed, 2008-04-16 at 13:51 -0300, Sérgio Durigan Júnior wrote:
Yes, it is a bug. What we want to know is if we should append $CFLAGS
to $BASECFLAGS (i.e., BASECFLAGS=$BASECFLAGS @CFLAGS@) or use *only*
$CFLAGS when the user provides it.
By convention and practice, the former (CFLAGS are ADDED
Hi Bob,
On Wed, 2008-04-16 at 11:24 -0500, Bob Friesenhahn wrote:
Does that mean that CFLAGS is a variable only for the user? Well, let's
say that, for some strong reason, the configure is actually modifying
it. What would be the correct behaviour in this case? FYI, I'm talking
On Wed, 16 Apr 2008, Sérgio Durigan Júnior wrote:
Yes, it is a bug. What we want to know is if we should append $CFLAGS to
$BASECFLAGS (i.e., BASECFLAGS=$BASECFLAGS @CFLAGS@) or use *only*
$CFLAGS when the user provides it.
Presumably BASECFLAGS exists for some useful purpose?
Don't forget
