From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Vincent Hanquez" Subject: Re: Endian safe mkelf32.c Date: Thu, 24 Feb 2005 14:52:04 +0100 Message-ID: <20050224135204.GA4866@snarc.org> References: <20050224121049.GA4411@snarc.org> <16925.51464.508636.126362@kitch0.watson.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16925.51464.508636.126362@kitch0.watson.ibm.com> Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Jimi Xenidis Cc: xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org 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