sysroot flags in $CC (was: [PATCH 3/3] ncurses: upgrade to 6.0+20160625)

[Enrico Scholz <enrico.scholz@sigma-chemnitz.de>]

"Burton, Ross" <ross.burton-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
writes:

>> This breaks the build with OE because it tries to split our $CC.
>> E.g. with
>>
>> | CC = ccache arm-linux-gnueabi-gcc -march=armv7ve ... --sysroot=...
>>
>> configure will warn
>>
>> | your environment misuses the CC variable to hold CFLAGS/CPPFLAGS options
>>
>> and messes up CFLAGS completely so that 'arm-linux-gnuebi-gcc' becomes
>> part of it :(
>>
>
> I've long wondered about changing our abuse of CC to hold the sysroot,

I do not think, that this is such a big abuse.  There are no flags
where these options can/should be placed instead of.  CPPFLAGS would
work for automake projects but lot of other buildsystems do not know
this variable.

Writing them into CFLAGS (and CXXFLAGS and FFLAGS and ...) would still
require them in CPPFLAGS too (for 'gcc -E' cases).  They will appear
twice (CPPFLAGS + xFLAGS) in automake project which is not a big deal
but a little bit ugly.


Enrico
-- 
SIGMA Chemnitz GmbH       Registergericht:   Amtsgericht Chemnitz HRB 1750
Am Erlenwald 13           Geschaeftsfuehrer: Grit Freitag, Frank Pyritz
09128 Chemnitz