On Monday 25 March 2013 12:51:07 Steve Dickson wrote:
> On 25/03/13 12:19, Mike Frysinger wrote:
> > On Monday 25 March 2013 08:42:32 Steve Dickson wrote:
> >> Also what exactly broke that this patch fixes?
> > 
> > also in my summary:
> > 	Newer autotools will use both CFLAGS and <target>_CFLAGS when compiling
> > 	the <target>.
> > 
> > so when you cross-compile (e.g. --build=x86_64-linux-gnu
> > --host=arm-linux- gnu), and you set CFLAGS to include settings which are
> > valid only for the host (e.g. -mfloat-abi=hard -mfp=neon), those flags
> > will also get passed to the build compiler when compiling these tools
> > and they'll error out (because the build gcc doesn't recognize these
> > flags).
> 
> And setting AM_CFLAGS does on take care of this problem...
> 
> I'm just trying to get rid of those warnings...

yeah, i don't know how to make it work w/out triggering the warnings :(.  
AM_CFLAGS is appended to CFLAGS rather than clobber it.

the concept of having build time tools is a bit foreign to automake atm, so we 
have to open code this stuff :/.
-mike