All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Kyle Russell <bkylerussell@gmail.com>, yocto@yoctoproject.org
Subject: Re: prelink support
Date: Mon, 20 Jun 2016 14:12:55 +0100	[thread overview]
Message-ID: <1466428375.3319.133.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAFrQVPMhmCAT+TfdOmQ95LsaTSc13=6GNvc=L=6cHmACGHRZgw@mail.gmail.com>

On Mon, 2016-06-20 at 08:24 -0400, Kyle Russell wrote:
> It looks like the image-prelink support is still disabled in master
> because of an issue with IFUNC symbol relocation.
> 
> https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta-poky/conf
> /local.conf.sample?id=8debfea81e69d038bd2d56314b272cb74f5582ed
> 
> Is there still a problem, or is it safe to reenable image-prelink?  I
> see a "Fix ARM IFUNC support" in the prelink-cross repo, but that
> appears to have been committed several months before image-prelink
> was disabled.  We'd like to enable image-prelink on a build off
> jethro.
> 
> Any help or links to a recent discussion thread would be helpful. 
> Thanks!

Basically, its still broken. I actually ran into a bug the other day
caused by the issue where I had prelink enabled locally.

I know Mark is working on some fixes but its an onion problem, you fix
one thing, then find other issues. Mark can give the full story but
right now, its not able to be re-enabled.

Cheers,

Richard


  reply	other threads:[~2016-06-20 13:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20 12:24 prelink support Kyle Russell
2016-06-20 13:12 ` Richard Purdie [this message]
2016-06-20 13:15 ` Mark Hatle
2016-06-20 13:45   ` Kyle Russell
2016-06-22  8:06   ` Kyle Russell
2016-06-22 14:57     ` Mark Hatle
2016-06-23  1:37       ` Kyle Russell

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=1466428375.3319.133.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bkylerussell@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.