public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: "André Draszik" <git@andred.net>
Cc: Yocto Discussion Mailing List <yocto@yoctoproject.org>,
	Richard Purdie <rpurdie@rpsys.net>,
	OpenEmbedded Devel List
	<openembedded-devel@lists.openembedded.org>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RFT] binutils 2.27
Date: Mon, 8 Aug 2016 08:21:32 -0700	[thread overview]
Message-ID: <ACB9AEF7-A7DF-4A88-9762-7569D91AD12D@gmail.com> (raw)
In-Reply-To: <1470647765.4581.23.camel@andred.net>

[-- Attachment #1: Type: text/plain, Size: 2393 bytes --]


> On Aug 8, 2016, at 2:16 AM, André Draszik <git@andred.net> wrote:
> 
> On Mon, 2016-08-08 at 09:50 +0100, Richard Purdie wrote:
>> On Mon, 2016-08-08 at 09:14 +0100, Richard Purdie wrote:
>>> 
>>> On Mon, 2016-08-08 at 00:24 -0700, Khem Raj wrote:
>>>> 
>>>>> 
>>>>> On Aug 7, 2016, at 11:28 PM, Richard Purdie <
>>>>> richard.purdie@linuxfoundation.org> wrote:
>>>>> 
>>>>> On Sun, 2016-08-07 at 01:39 -0700, Khem Raj wrote:
>>>>>> 
>>>>>> I have put together upgrade for binutils 2.27 here (
>>>>>> kraj/master
>>>>>> branch )
>>>>>> 
>>>>>> https://github.com/kraj/openembedded-core/commit/b98f5761d2285f
>>>>>> fd
>>>>>> 773e
>>>>>> c6ecb901b799302ebd6b
>>>>>> 
>>>>>> I have started bunch of test builds. but I would appreciate any
>>>>>> help
>>>>>> in testing it out in your
>>>>>> environments and report any issues you see.
>>>>> 
>>>>> I ran this through the autobuilder:
>>>>> 
>>>>> bitbake world shows issues in libunwind (from gold?):
>>>>> 
>>>> 
>>>> yes, however, use of gold for libunwind in OE was an escape route
>>>> where we were relying upon gold’s inability to detect this issue
>>>> while BFD linker
>>>> was detecting it earlier. Now in 2.27 gold has caught up as well.
>>>> 
>>>> see
>>>> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6eeb0170
>>>> bb
>>>> b43ffb73e8f01b8b481adde8194c21
>>>> 
>>>> so now we have to get to nub of this issue to resolve it.
>>> 
>>> Ok. I think we also have:
>>> 
>>> https://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds
>>> /8
>>> 96
>>> https://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds
>>> /8
>>> 96
>>> 
>>> in that "connmand --help" is segfaulting on ppc. I've not 100%
>>> confirmed its the binutils patch but its seeming likely at this
>>> point.
>> 
>> Its also sefgaulting on all mips builds:
>> 
>> https://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/883
>> https://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds
>> /863
>> https://autobuilder.yoctoproject.org/main/builders/nightly-mips64/builds/5
>> 28
>> 
>> :(
> 
> binutils 2.27 brings GOLD to mips, but debian has disabled GOLD on all MIPS
> for now due to segfaulting... Maybe the same issue…

They are different issues. for OE ppc also shows same errors with libunwind.

> 
> 
> A.
> 
> 


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

  reply	other threads:[~2016-08-08 15:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-07  8:39 [RFT] binutils 2.27 Khem Raj
2016-08-08  6:28 ` Richard Purdie
2016-08-08  7:24   ` Khem Raj
2016-08-08  8:14     ` Richard Purdie
2016-08-08  8:50       ` Richard Purdie
2016-08-08  9:16         ` André Draszik
2016-08-08 15:21           ` Khem Raj [this message]
2016-08-08 15:59             ` Richard Purdie
2016-08-08 23:16               ` Burton, Ross
2016-08-09 14:42                 ` Khem Raj
2016-08-09 15:24                   ` Richard Purdie
2016-08-10 15:25                     ` [oe] " Martin Jansa
2016-08-08 23:06   ` Khem Raj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ACB9AEF7-A7DF-4A88-9762-7569D91AD12D@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=git@andred.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=rpurdie@rpsys.net \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox