From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mm3wl-0004Hf-8p for qemu-devel@nongnu.org; Fri, 11 Sep 2009 07:05:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mm3we-0004BC-Sv for qemu-devel@nongnu.org; Fri, 11 Sep 2009 07:05:41 -0400 Received: from [199.232.76.173] (port=54853 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mm3we-0004Az-9s for qemu-devel@nongnu.org; Fri, 11 Sep 2009 07:05:36 -0400 Received: from mail.gmx.net ([213.165.64.20]:34699) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1Mm3wd-0003wl-FO for qemu-devel@nongnu.org; Fri, 11 Sep 2009 07:05:35 -0400 Content-Type: text/plain; charset="us-ascii" Date: Fri, 11 Sep 2009 13:05:32 +0200 From: "Johannes Luber" In-Reply-To: Message-ID: <20090911110532.291800@gmx.net> MIME-Version: 1.0 References: <20090911093913.324670@gmx.net> Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: target_phys_addr_t definition List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Juan Quintela Cc: qemu-devel@nongnu.org > "Johannes Luber" wrote: ... > So my question is: Does Qemu support 64-bit compilation > for hosts correctly? > > > > Best regards, > > Johannes > > Dragons here. > > See configure, the interesting bit is: > > if [ $target_phys_bits -lt $hostlongbits ] ; then > target_phys_bits=$hostlongbits > fi > > TARGET_PHYS_ADDR_BITS is the maximum of host + target long sizes. > > Later, Juan. Thanks for the quick response! It seems that someone edited my local config.h which resulted in losing the config-host.h. It would be nice if something like #ifndef HOST_LONG_BITS #error No HOST_LONG_BITS #endif could be included at appropriate places. This would make this problem self-evident in the future. Best regards, Johannes -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser