From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] Fix 64-bit foreign header check Date: Wed, 15 Aug 2007 15:59:49 +0100 Message-ID: References: <20070815143716.GA8459@barman.uk.sun.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070815143716.GA8459@barman.uk.sun.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: John Levon Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 15/8/07 15:37, "John Levon" wrote: >> Won't gcc produce 64-bit binaries by default in a 64-bit environment? > > There is no such thing as a "64-bit environment" on Solaris, all machines ship > with both 32 and 64 bit functionality (of course the kernel must be 64-bit to > actually /use/ such). > > Thus we build twice, once in 32-bit, once in 64-bit. Then isn't your TARGET_ARCH!=COMPILE_ARCH for one of these builds? Sounds like you have a 32-bit-ish compile environment (since you produce 32-bit binaries by default), and hence it would be correct to have COMPILE_ARCH==x86_32 for both builds. -- Keir