From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] Update prelinker to latest upstream version
Date: Tue, 6 Sep 2011 11:26:51 -0500 [thread overview]
Message-ID: <cover.1315326300.git.mark.hatle@windriver.com> (raw)
Update the prelinker to the latest (yoctoproject) cross_prelinker version.
This syncs to the latest Red Hat version, provides a new rtld emulation, and
now can identify bad GNU_HASH entries to help detect a bug in the hash
generation observed on PPC64.
The following changes since commit 41b7c955cfdc7b4d5c667c8a8742237d5edaca4f:
icu-3.6: fix building with big make -j (2011-09-05 20:38:50 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib mhatle/prelink
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/prelink
Mark Hatle (1):
prelink: Update to latest upstream version
meta/recipes-devtools/prelink/prelink_git.bb | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
--
1.7.3.4
next reply other threads:[~2011-09-06 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 16:26 Mark Hatle [this message]
2011-09-06 16:26 ` [PATCH 1/1] prelink: Update to latest upstream version Mark Hatle
2011-09-08 3:46 ` [PATCH 0/1] Update prelinker " Saul Wold
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.1315326300.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