All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Mark Hatle <mark.hatle@windriver.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Prelink problems -- need help!
Date: Mon, 26 Oct 2015 16:10:41 +0000	[thread overview]
Message-ID: <1445875841.5251.107.camel@pbcl.net> (raw)
In-Reply-To: <562E3896.6080405@windriver.com>

[Cc list trimmed]

On Mon, 2015-10-26 at 09:28 -0500, Mark Hatle wrote:
> As you can see, pretty much everything is currently broken and I'm
> struggling to
> find community people with the right skill sets to help me resolve
> the issues.

I think it's true that prelink is a technology which has largely had
its day, and I could well imagine that upstream Red Hat is no longer
very interested in it.  https://fedorahosted.org/fesco/ticket/1183 has
a summary of some of the reasons why.

Before investing any significant amount of time in fixing up prelink
(and from what you've described it sounds like it might indeed be a
significant effort to get it working again on all platforms) it might
be a good idea to make sure we are still convinced that prelink
provides useful and meaningful benefits for OE-core users.

If the answer to that is yes then I probably could spare a bit of time
to look at the ARM and MIPS issues at least. 

p.



  reply	other threads:[~2015-10-26 16:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26 14:28 Prelink problems -- need help! Mark Hatle
2015-10-26 16:10 ` Phil Blundell [this message]
2015-10-26 16:45   ` Mark Hatle
2015-10-26 16:50     ` Phil Blundell
2015-10-26 16:55       ` Mark Hatle
2015-10-26 21:18         ` Phil Blundell
2015-10-26 21:35           ` Mark Hatle
2015-10-29 18:32         ` Khem Raj
2015-10-29 18:41           ` Mark Hatle
2015-10-27  0:40     ` Mark Hatle
2015-10-30  3:50 ` Prelink status 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=1445875841.5251.107.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 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.