[OE-core] [RFT] gcc 6.2 RC1 update

[Khem Raj]

> On Aug 19, 2016, at 8:05 AM, Gary Thomas <gary at mlbassoc.com> wrote:
> 
> On 2016-08-19 16:59, Khem Raj wrote:
>> This is a long standing assembler error. Which I never get to bottom of. Rwboorinf the build machine helps
>                                                                           ^^^^^^^^^
> 
> What does this mean?  As I mentioned, it worked fine before you updated to 6.2

‘rebooting’, ( blame the phone keyboard) this is a memory block that returns wrong string and somehow related to allocations in assembler, if its the same error as I know of. It does not have to do with
gcc.

> 
>> 
>> 
>> On Aug 19, 2016 7:06 AM, "Gary Thomas" <gary at mlbassoc.com <mailto:gary at mlbassoc.com>> wrote:
>> 
>>    On 2016-08-19 16:04, Gary Thomas wrote:
>> 
>>        On 2016-08-19 15:40, Khem Raj wrote:
>> 
>> 
>>                On Aug 19, 2016, at 3:14 AM, Richard Purdie <richard.purdie at linuxfoundation.org
>>                <mailto:richard.purdie at linuxfoundation.org>> wrote:
>> 
>>                On Tue, 2016-08-16 at 11:55 -0700, Khem Raj wrote:
>> 
>>                    Hi All
>> 
>>                    I have put together recipe upgrade for upcoming gcc 6.2 release now
>>                    that it entered RC phase. With gcc 6.2 the recipes are using tarballs
>>                    instead of git fetcher as promised :)
>>                    Please help testing it out in your setups and report any issues you
>>                    see.
>> 
>>                    The commit you need to cherry-pick for OE-core is this one
>> 
>>                    https://github.com/kraj/openembedded-core/commit/0319b603761a16e65d70
>>                    <https://github.com/kraj/openembedded-core/commit/0319b603761a16e65d70>
>>                    4336112c3709a8bf771c
>> 
>>                    Thank you for your help
>> 
>> 
>>                I put this through the autobuilder and it passed so I've merged it. I
>>                did this quickly as we're putting a "pre M3" build through a QA cycle
>>                and I wanted to get some of the more invasive changes into that build
>>                so we don't have a stampeding herd of patches breaking everything
>>                coming up to the final feature freeze for 2.2.
>> 
>>                In other news, we are now also testing musl world builds on the
>>                autobuilder as part of regular testing.
>> 
>> 
>>            Fantastic !
>> 
>> 
>>        Problem using this to build meta-fsl-arm:u-boot-fslc for i.MX6:
>>            CC      lib/asm-offsets.s
>>            lib/asm-offsets.c:1:0: error: bad value (armv5) for -march= switch
>> 
>>        This worked fine with GCC/6.1 (git)
>> 
>>        Ideas?
>> 
>> 
>>    Also, the bitbake "do_compile log" didn't show me this at all,
>>    I had to get it by running 'bitbake u-boot-fslc -c devshell' and
>>    then 'make' to see the error :-(
> 
> --
> ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------------------------------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160819/78115847/attachment-0002.sig>