On 21 February 2017 at 13:50, Burton, Ross wrote:
> I'm a big fan of fixing upstream so we don't have to carry a patch
> forever. Their rationale I don't understand, but the implementation is
> clearly broken.
>
Here's my current fix:
+ cf_flags=`echo "$CC" | awk 'BEGIN{ORS=" ";RS=" "} /
On 21 February 2017 at 01:34, Hongxu Jia wrote:
> How about directly remove the cf_flags assigning? Because our OE have
> correctly assigned it in bitbake.conf.
>
I'm a big fan of fixing upstream so we don't have to carry a patch
forever. Their rationale I don't understand, but the implementati
In configure, the option ${HOST_CC_ARCH} was removed from ${CC}:
---
|configure:2188: WARNING: your environment misuses the CC variable
to hold CFLAGS/CPPFLAGS options
|configure:2284: testing resulting CC: 'arm-poky-linux-gnueabi-gcc
--sysroot=tmp/work/cortexa8hf-neon-poky-linux-gnueab
On 2017年02月21日 09:01, Enrico Scholz wrote:
"Burton, Ross" writes:
c) fix the function that detects the "broken" use of CC as it should be
extracting the flags and moving them to CFLAGS. Clearly this isn't working
somewhere.
Upstream tries to do it correctly for nearly a year and fails everyt
"Burton, Ross" writes:
>> c) fix the function that detects the "broken" use of CC as it should be
>> extracting the flags and moving them to CFLAGS. Clearly this isn't working
>> somewhere.
Upstream tries to do it correctly for nearly a year and fails everytime
at some cornercases.
> I've a l
On 20 February 2017 at 23:21, Burton, Ross wrote:
> c) fix the function that detects the "broken" use of CC as it should be
> extracting the flags and moving them to CFLAGS. Clearly this isn't working
> somewhere.
>
So upstream's sed made the assumption that there was only one argument
being pa
On 14 February 2017 at 10:48, Enrico Scholz wrote:
> a) bother the ncurses author to remove the stupid CC sanity check, or
>
> b) create a wrapper around CC like in
>
c) fix the function that detects the "broken" use of CC as it should be
extracting the flags and moving them to CFLAGS. Clearly
Hongxu Jia writes:
> Append ${HOST_CC_ARCH} to ${CFLAGS} could fix the issue.
I think, the correct fix would be
a) bother the ncurses author to remove the stupid CC sanity check, or
b) create a wrapper around CC like in
https://github.com/sigma-embedded/elito-de.sigma-chemnitz/blob/master
In configure, the option ${HOST_CC_ARCH} was removed from ${CC}:
---
|configure:2188: WARNING: your environment misuses the CC variable
to hold CFLAGS/CPPFLAGS options
|configure:2284: testing resulting CC: 'arm-poky-linux-gnueabi-gcc
--sysroot=tmp/work/cortexa8hf-neon-poky-linux-gnueab
