From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] prelink changes
Date: Fri, 19 Aug 2016 20:44:53 -0500 [thread overview]
Message-ID: <cover.1471657381.git.mark.hatle@windriver.com> (raw)
Re-enable prelink on ARM and PPC. The detected failures are not related to
anything inside of prelink, the binaries failed to execute before prelinking.
The other patch fixes the IFUNC resolution problem inside of glibc itself.
The scope was being resolved depth first, not breadth first as indicated in
the ELF specification.
The following changes since commit d3e5c1d17f80b3dd7a6d85e07b5c0c516f09ae93:
local.conf.sample: Disable ARM and PPC due to prelink test case failures (2016-08-19 10:23:31 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib mhatle/prelink
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=mhatle/prelink
Mark Hatle (2):
glibc: Fix scope resolution in glibc to be breadth first.
Revert "local.conf.sample: Disable ARM and PPC due to prelink test
case failures"
meta/conf/local.conf.sample | 9 ----
.../glibc/glibc/0026-build_local_scope.patch | 56 ++++++++++++++++++++++
meta/recipes-core/glibc/glibc_2.24.bb | 1 +
3 files changed, 57 insertions(+), 9 deletions(-)
create mode 100644 meta/recipes-core/glibc/glibc/0026-build_local_scope.patch
--
2.5.5
next reply other threads:[~2016-08-20 1:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-20 1:44 Mark Hatle [this message]
2016-08-20 1:44 ` [PATCH 1/2] glibc: Fix scope resolution in glibc to be breadth first Mark Hatle
2016-08-20 2:17 ` Mark Hatle
2016-08-20 1:44 ` [PATCH 2/2] Revert "local.conf.sample: Disable ARM and PPC due to prelink test case failures" 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=cover.1471657381.git.mark.hatle@windriver.com \
--to=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