Re: [Xen-devel] Endian safe mkelf32.c

On Thu, Feb 24, 2005 at 07:31:04AM -0500, Jimi Xenidis wrote:
>  VH> This looks wrong. The endianess is figured by e.ident[EI_DATA] not by
>  VH> reading e_type to see if we can recognize the type in all endianess.
> 
> This test is discover if the build machine is the same endian of the
> image or not.

make sense. I assumed, because of x86 directory in the path, that only
cross-compiler would compile that, but indeed that's just a tool.

sorry for the noise :)

-- 
Vincent Hanquez


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] Endian safe mkelf32.c, Jimi Xenidis Re: [Xen-devel] Endian safe mkelf32.c, Vincent Hanquez Re: [Xen-devel] Endian safe mkelf32.c, Jimi Xenidis Re: [Xen-devel] Endian safe mkelf32.c, Vincent Hanquez <=

Previous by Date:

Re: [Xen-devel] Calculating real cpu usage of Xen domains correctly!, Stephan Diestelhorst

Next by Date:

Re: [Xen-devel] Crash, visik7

Previous by Thread:

Re: [Xen-devel] Endian safe mkelf32.c, Jimi Xenidis

Next by Thread:

[Xen-devel] [patch] add console_use_vt check, Gerd Knorr

Indexes:

[Date] [Thread] [Top] [All Lists]