[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openembedded-core
Subject:    [OE-core] ldconfig-native is not endian safe
From:       nitin.a.kamble () intel ! com (Kamble, Nitin A)
Date:       2011-03-31 17:27:02
Message-ID: 9DA5872FEF993D41B7173F58FCF6BE945111C624 () orsmsx504 ! amr ! corp ! intel ! com
[Download RAW message or body]



> -----Original Message-----
> From: openembedded-core-bounces at lists.openembedded.org
> [mailto:openembedded-core-bounces at lists.openembedded.org] On Behalf Of
> Richard Purdie
> Sent: Thursday, March 31, 2011 3:41 AM
> To: Patches and discussions about the oe-core layer
> Subject: Re: [OE-core] lconfig-native is not endian safe
> 
> 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
> 

Richard,
  I upgraded ldconfig-native to 2.12.1 ( our eglibc version), I rebased your patch to \
it, and will implement rest of the endianness handling code. Thanks,
Nitin

> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core


[prev in list] [next in list] [prev in thread] [next in thread]