Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: lconfig-native is not endian safe
Date: Thu, 31 Mar 2011 11:40:31 +0100	[thread overview]
Message-ID: <1301568031.24596.104.camel@rex> (raw)
In-Reply-To: <A1E6FA6F-3108-4E38-8E8F-2F231E6E1685@windriver.com>

On Thu, 2011-03-31 at 09:02 +0000, Hatle, Mark wrote:
> My opinion is to avoid it vs run in a qemu shell.  I really don't like
> being forced to have qemu to run a build of any type.

Agreed, I think we can avoid this.

For reference, I have half he endian problem resolved with:

http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/gcc-sharedwork&id=0711c7c065c6e1caa04f452069d08a056c3caabe

which handles reading in the data from the elf files in an endian safe
way. Someone needs to go through and change the dl cache file handling
code to be endian safe though, then compare the result with a file
generated on a target device.

Cheers,

Richard





  reply	other threads:[~2011-03-31 10:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 14:47 lconfig-native is not endian safe Richard Purdie
2011-03-30 15:43 ` Mark Hatle
2011-03-31  1:59   ` Kamble, Nitin A
2011-03-31  2:02     ` Kamble, Nitin A
2011-03-31  2:09       ` Kamble, Nitin A
2011-03-31  9:02         ` Hatle, Mark
2011-03-31 10:40           ` Richard Purdie [this message]
2011-03-31 17:27             ` ldconfig-native " Kamble, Nitin A
2011-04-05  2:15         ` lconfig-native " Khem Raj

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=1301568031.24596.104.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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