public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: Yocto Discussion Mailing List <yocto@yoctoproject.org>,
	OpenEmbedded Devel List
	<openembedded-devel@lists.openembedded.org>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RFT] binutils 2.27
Date: Mon, 08 Aug 2016 09:14:54 +0100	[thread overview]
Message-ID: <1470644094.8166.37.camel@linuxfoundation.org> (raw)
In-Reply-To: <8C207C42-3D61-4C3F-A1DE-F305AA6617BA@gmail.com>

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/b98f5761d2285ffd
> > > 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=6eeb0170bb
> 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.

Cheers,

Richard


  reply	other threads:[~2016-08-08  8:14 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 [this message]
2016-08-08  8:50       ` Richard Purdie
2016-08-08  9:16         ` André Draszik
2016-08-08 15:21           ` Khem Raj
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=1470644094.8166.37.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --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