From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] Update to latest prelinker -- fix arm and x86 issues
Date: Wed, 14 Sep 2011 10:03:38 -0700 [thread overview]
Message-ID: <1316019818.1058.28.camel@swold-mobl.bigsur.com> (raw)
In-Reply-To: <cover.1315961467.git.mark.hatle@windriver.com>
On Tue, 2011-09-13 at 19:52 -0500, Mark Hatle wrote:
> This fixes yocto bugzilla bug 1473. It addresses an issue where a typecast
> wasn't being specified and the compiler was doing the wrong thing in a
> printf.
>
> The symbols of the previous failure were, on a 32-bit IA32 host, targeting
> either a 32-bit IA32 target or ARM target the results of a prelinked image
> may not work properly.
>
Mark,
There is still a problem with the prelinker, it seems to clobber text in
X11 on qemux86, we get a build that has square blocks for text.
Sau!
> The following changes since commit 3be290aac4da885fe5bc31797c4a689196c63b7a:
>
> libzypp: move package-manger to it own package (2011-09-13 16:19:30 -0700)
>
> 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):
> Uprev to latest version of prelink_git, fixing TLS issues
>
> meta/recipes-devtools/prelink/prelink_git.bb | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2011-09-14 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 0:52 [PATCH 0/1] Update to latest prelinker -- fix arm and x86 issues Mark Hatle
2011-09-14 0:52 ` [PATCH 1/1] Uprev to latest version of prelink_git, fixing TLS issues Mark Hatle
2011-09-14 0:53 ` Mark Hatle
2011-09-14 17:03 ` Saul Wold [this message]
2011-09-14 17:11 ` [PATCH 0/1] Update to latest prelinker -- fix arm and x86 issues Zhang, Jessica
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=1316019818.1058.28.camel@swold-mobl.bigsur.com \
--to=sgw@linux.intel.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