From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Khem Raj" <raj.khem@gmail.com>, "André Draszik" <git@andred.net>
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 16:59:51 +0100 [thread overview]
Message-ID: <1470671991.8166.44.camel@linuxfoundation.org> (raw)
In-Reply-To: <ACB9AEF7-A7DF-4A88-9762-7569D91AD12D@gmail.com>
On Mon, 2016-08-08 at 08:21 -0700, Khem Raj wrote:
> They are different issues. for OE ppc also shows same errors with lib
> unwind.
FWIW, I think the connmand segfault on mips and powerpc is hinted at
with this bug:
https://bugs.launchpad.net/ubuntu/+source/lua5.3/+bug/1570055
connmand is a binary linked with a linker version-script. If I build
connmand without that option, it doesn't segfault, at least on mips.
The binutils manuals say you shouldn't build binaries with version
scripts:
http://ftp.gnu.org/old-gnu/Manuals/ld-2.9.1/html_node/ld_25.html
Its suspected connman might do this to limit the function exposure to
its plugins.
Now sure exactly what needs to happen here without more research but it
certainly hits at where the problem is. I suspect its the same issue on
ppc.
Cheers,
Richard
next prev parent reply other threads:[~2016-08-08 16:00 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
2016-08-08 15:59 ` Richard Purdie [this message]
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=1470671991.8166.44.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=git@andred.net \
--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