From: Mark Hatle <mark.hatle@windriver.com>
To: Yocto Project <yocto@yoctoproject.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
<openembedded-devel@lists.openembedded.org>
Subject: Prelink problems -- need help!
Date: Mon, 26 Oct 2015 09:28:38 -0500 [thread overview]
Message-ID: <562E3896.6080405@windriver.com> (raw)
I'm cross posting this in an effort to ask for help for the cross-prelink
project. (If you are unaware of what the prelinker does, it goes through and
adjusts the relocation addresses to predefined values in an attempt to speed up
executable load times. For embedded systems, this can be fairly critical in
meeting boot and runtime load performance targets.)
As some people might be aware, the upstream 'prelink' project that was
maintained by Jakub Jelinek at Red Hat appears to have been abandoned.
I've been the maintainer for the Yocto Project's 'prelink-cross' project for a
few years, but my work has been dealing with compilation issues and other things
that have to do with using the prelinker in a cross compilation environment.
This means that unfortunately I'm in a situation where I am having problems
trying to fix the problems in the prelinker itself, but I am not an ELF expert.
Currently the cross prelinker appears to be broken for pretty much every
architecture and I need help trying to resolve these problems.
Issues I know of right now:
Introduction of RTYPE_CLASS_EXTERN_PROTECTED_DATA appears to be causing failures
on ARM32, x86 and x86_64.
Some possibly unrelated issue is causing various items to relocate incorrectly
(IFUNCs perhaps) on ARMv7 builds.
Power is no longer working properly, most likely due to an optimization in the
way the PPC GOT table(s) are setup.
Power64 hasn't been working properly for a while, possibly due to the switch to
ELFv2.
MIPS and MIPS64 also do not appear to be working, and I've not found a possible
cause.
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.
The current state of my work in progress is available at:
git://git.yoctoproject.org/prelink-cross
branch cross_prelink_staging
If you think you can help, please let me know.
--Mark
next reply other threads:[~2015-10-26 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 14:28 Mark Hatle [this message]
2015-10-26 16:10 ` Prelink problems -- need help! Phil Blundell
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=562E3896.6080405@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--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.