Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] prelink: Move to latest release
Date: Mon, 14 Sep 2015 20:59:24 +0100	[thread overview]
Message-ID: <1442260764.2948.90.camel@pbcl.net> (raw)
In-Reply-To: <1442245637-140022-1-git-send-email-mark.hatle@windriver.com>

On Mon, 2015-09-14 at 10:47 -0500, Mark Hatle wrote:
> [YOCTO #8227]
> 
> The latest release has a fix for prelinking on ARM with recent binutils.
> 
> For more information on why the change was necessary, see:
> 
>   https://sourceware.org/ml/binutils/2014-06/msg00228.html

That link isn't particularly illuminating for someone not well versed in
the art of prelink.  I assume the significant thing is that the default
MAXPAGESIZE has changed for arm, but it's not entirely obvious why this
matters to prelink, what problem it caused, or what the change in
prelink is that fixes the problem.  Can you elaborate?

thanks

p.




  reply	other threads:[~2015-09-14 19:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 15:47 [PATCH] prelink: Move to latest release Mark Hatle
2015-09-14 19:59 ` Phil Blundell [this message]
2015-09-14 20:21   ` Mark Hatle

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=1442260764.2948.90.camel@pbcl.net \
    --to=pb@pbcl.net \
    --cc=mark.hatle@windriver.com \
    --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