From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH] prelink: Added prelink-20100106, which works on ARM.
Date: Wed, 15 Jun 2011 09:08:33 -0500 [thread overview]
Message-ID: <4DF8BCE1.8030202@windriver.com> (raw)
In-Reply-To: <840A81C1B782724A8EB52725BD519EFF02EAF4@MBX20.4emm.local>
On 6/15/11 4:18 AM, James Limbouris wrote:
> On Tue, 14 Jun 2011 22:20:18 -0500, Mark Hatle wrote:
>> On 6/14/11 10:02 PM, Mark Hatle wrote:
>>> Have you looked at:
>>>
>>> http://git.yoctoproject.org/cgit/cgit.cgi/prelink-cross/
>>>
>>> As far as I'm aware, this version works properly for all of the expected
>>> targets, including ARM.
>>>
>>> If it doesn't work, someone should submit a patch to the maintainer (me)
>> and
>>> we'll get things resolved.
>>>
>>> The Yocto prelinker contains both local (on-target) as well as cross-
>> prelinking
>>> support... (This is already integrated into oe-core)
>>
>> Forgot to note, look at the cross_prelink branch. This is the head of tree for
>> the embedded items. The "master" is a mirror of the current SVN tree from
>> Jakub
>> Jelinek.
>>
>> The ld-linux... patch hunk is already there, and in a better shape then the one
>> proposed. Both the ld-linux.so.2 and ld-linux.so.3 are supported.
>>
>>> --Mark
>
> Hi,
>
> Thanks for the link - looks like the right way to go. Would it be a waste of time to copy
> the oe-core prelink and elfutils to vanilla oe? I'm a little confused about the relationship
> between the two branches, and the status of oe-core. Should I be working with local
> overlays, until things stabilise, or trying to push changes across?
While I haven't tried to do so, I would expect the recipes from oe-core for
prelink and elfutils to work pretty much as-is. There might be a few very minor
tweaks required, but it would be minor.
--Mark
> James
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2011-06-15 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 9:18 [PATCH] prelink: Added prelink-20100106, which works on ARM James Limbouris
2011-06-15 14:08 ` Mark Hatle [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-15 1:33 James Limbouris
2011-06-14 7:49 James Limbouris
2011-06-14 9:16 ` Phil Blundell
2011-06-15 1:16 ` James Limbouris
2011-06-15 3:02 ` Mark Hatle
2011-06-15 3:20 ` Mark Hatle
2011-06-14 12:37 ` Paul Menzel
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=4DF8BCE1.8030202@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-devel@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.