[OE-core] [PATCH 4/6] tcmode-default: Bump gcc,glibc,gdb

Bruce Ashfield bruce.ashfield at windriver.com
Wed May 25 12:32:55 UTC 2016


On 2016-05-25 2:39 AM, Richard Purdie wrote:
> Thanks to the patches from Bruce we're looking better, linux-yocto 4.1
> works, just 4.4 has a couple of issues. I also removed a patch which
> removed the xdg-utils failure. That leaves us with:
>
> qt4-x11-free:
>
> arm, mips, ppc, world-lsb, x86, x86_64:
> https://autobuilder.yoctoproject.org/main/builders/nightly-arm-lsb/buil
> ds/767/steps/BuildImages/logs/stdio
>
> qt4-embedded:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-world-lsb/bu
> ilds/520/steps/BuildImages/logs/stdio
>
> linux-yocto-4.4 mips:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/
> 795/steps/BuildImages_1/logs/stdio
>
> linux-yocto-4.4 ppc:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/8
> 07/steps/BuildImages_1/logs/stdio
>
> diffutils - non-gplv3:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-non-gpl3/bui
> lds/797
>
> Bruce: Looks like 4.4 might also need a patch you merged to 4.1?

I didn't see anything obvious missing from 4.4, and the existing patches
posted for the build issues are part of:

-----------------

commit 574e9f4b4334807faad40a2d23c350f266d6febb
Author: Bruce Ashfield <bruce.ashfield at windriver.com>
Date:   Fri May 13 09:46:53 2016 -0700

     linux-yocto/4.4: gcc6 build fixes (powerpc and mips)

     Khem provided fixes to fix gcc6 build issues, these are safe for
     all gcc versions, so we integrate them directly.

     (From OE-Core rev: f1c75b93a4e11425e595c5ce043fbb0276a41931)

     Signed-off-by: Khem Raj <raj.khem at gmail.com>
     Signed-off-by: Bruce Ashfield <bruce.ashfield at windriver.com>
     Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>

---------------

So I can't say why the two build failures that that commit addresses
are popping up.

I checked and the later 4.4-stable commit update I did has the right
SRCREVs and encompasses that fix .. unless something ended up getting
clobbered in the code itself.

What's the right incantation to start a gcc6 based build on my own
machine ? Just bump the preferred version of the compiler ? (I'll do
that now, since I see the gcc6 recipe .. and that seems like the
obvious thing).

Bruce

>
> Cheers,
>
> Richard
>




More information about the Openembedded-core mailing list