From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: MIPS Prelinker problem -- possible fix
Date: Fri, 06 Jan 2012 13:25:58 +0000 [thread overview]
Message-ID: <1325856358.28005.179.camel@phil-desktop> (raw)
In-Reply-To: <4F05CAB9.4020001@windriver.com>
On Thu, 2012-01-05 at 10:07 -0600, Mark Hatle wrote:
> I have created a patch (with help from Khem Raj) to resolve a long standing
> issue w/ the MIPS prelinker. The prelinker was detecting a error condition
> based on what appears to be some incomplete math calculations.
>
> Attached is a patch that I believe will fix the problem, but I would like folks
> on both MIPS and non MIPS system to try it out.
Thanks. I tried this out last night and it does seem to solve the
problem for me. (I was previously using a hack in image-prelink.bbclass
which just deleted all the .mdebug.abi32 sections before prelinking.)
p.
prev parent reply other threads:[~2012-01-06 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 16:07 MIPS Prelinker problem -- possible fix Mark Hatle
2012-01-06 13:25 ` Phil Blundell [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=1325856358.28005.179.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.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