From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] binutils: Add fixes for binutils issue 16428
Date: Tue, 25 Mar 2014 12:21:58 +0000 [thread overview]
Message-ID: <1395750118.24890.26.camel@ted> (raw)
In-Reply-To: <CAP9ODKr4icx=rWteGJ_o9zA2Czkn8ZOjMOAqmT3LwxJY79VZKw@mail.gmail.com>
On Tue, 2014-03-25 at 09:13 -0300, Otavio Salvador wrote:
> On Tue, Mar 25, 2014 at 7:36 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > "ld:i386 crashes with -static -fPIE -pie"
> > https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1266492
> >
> > This adds in two upstream binutils fixes to avoid the internal error
> > triggered by the combination of -static with -pie on x86 builds. This
> > triggers a backtrace which then triggers a bug in glibc where the process
> > ends up hanging on some systems with broken libcs.
> >
> > We can't fix the libc but we can stop the internal error and hence
> > avoid the hanging builds.
> >
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > + file://fix-pr16428a.patch \
> > + file://fix-pr16428b.patch \
>
> Please add the Upstream-Status field in the two patch files stating
> this is a 'Backport'.
Well spotted, I did realise this after I sent the patch and I've already
updated the version in master-next which is testing more widely at the
moment.
Cheers,
Richard
prev parent reply other threads:[~2014-03-25 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 10:36 [PATCH] binutils: Add fixes for binutils issue 16428 Richard Purdie
2014-03-25 12:13 ` Otavio Salvador
2014-03-25 12:21 ` Richard Purdie [this message]
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=1395750118.24890.26.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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