From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jac3E-0006nJ-FN for qemu-devel@nongnu.org; Sat, 15 Mar 2008 15:28:16 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jac3C-0006n4-2M for qemu-devel@nongnu.org; Sat, 15 Mar 2008 15:28:15 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jac3B-0006n1-SK for qemu-devel@nongnu.org; Sat, 15 Mar 2008 15:28:13 -0400 Received: from mx2.suse.de ([195.135.220.15]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Jac3B-00027T-D6 for qemu-devel@nongnu.org; Sat, 15 Mar 2008 15:28:13 -0400 Received: from Relay2.suse.de (mail2.suse.de [195.135.221.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx2.suse.de (Postfix) with ESMTP id 315743BBD1 for ; Sat, 15 Mar 2008 20:28:10 +0100 (CET) Message-ID: <47DC2744.9090602@suse.de> Date: Sat, 15 Mar 2008 20:45:08 +0100 From: Alexander Graf MIME-Version: 1.0 Subject: Re: [Qemu-devel] build failure on x86, any suggestions? References: <1205589710.24804.65.camel@localhost> <200803151420.25502.paul@codesourcery.com> <1205593982.24804.78.camel@localhost> In-Reply-To: <1205593982.24804.78.camel@localhost> Content-Type: multipart/mixed; boundary="------------060001060307050601080704" Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org This is a multi-part message in MIME format. --------------060001060307050601080704 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Peter Volkov wrote: > =D0=92 =D0=A1=D0=B1=D1=82, 15/03/2008 =D0=B2 14:20 +0000, Paul Brook =D0= =BF=D0=B8=D1=88=D0=B5=D1=82: > =20 >> On Saturday 15 March 2008, Peter Volkov wrote: >> =20 >>> Hello. >>> >>> I just wanted to point developers attention to the following bug: >>> bugs.gentoo.org/212351 , comment #11 and further. The problem is that >>> qemu does not compile any more on x86. I've tried recent snapshot >>> (2008-03-15_05) and the problem persist there. >>> =20 >> You're almost certainly using gcc4.x. Don't do that. >> =20 > > Paul, thank you for you answer. I do have gcc-4 installed on my system > but I'm sure that I'm using gcc-3.4: > > =20 >> gcc --version >> =20 > gcc (GCC) 3.4.6 (Gentoo 3.4.6-r2 p1.5, ssp-3.4.6-1.0, pie-8.7.10) > > As I read FAQ this version should be supported. I've tried to build gcc > without patches (ssp, pie, C++ support and some gentoo specific patches= ) > but qemu build process still fails at the same place... > > =20 >> IIRC gentoo already has a big pile hacks for this. This kind of breaka= ge is=20 >> exactly why those hacks haven't been merged into cvs. They're papering= over=20 >> the problem rather than fixing it, so you should expect them to need c= onstant=20 >> maintenance. >> =20 > > Sorry, but what hacks are you talking about? The only hack I'm aware > about is that all system is build with newer compiler while to build > qemu I have to install old gcc. > > =20 >> As mentioned several times on this recently on this list, the proper f= ix is to=20 >> finish the TCG conversion. That will happen "when it's done". >> =20 > > Eh, I saw you talking about this and I'm aware that this will definitel= y > take time. That's why I asked for suggestion... > > =20 For the time being you could try the appended patch. It makes x86 on x86 slower though, but should enable you to have a working build at all. I am not 100% sure if it actually does help in your case though. Alex --------------060001060307050601080704 Content-Type: text/x-patch; name="qemu-reghack.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="qemu-reghack.patch" --- a/target-i386/op.c +++ b/target-i386/op.c @@ -18,7 +18,7 @@ * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA */ -#define ASM_SOFTMMU +//#define ASM_SOFTMMU #include "exec.h" /* n must be a constant to be efficient */ --------------060001060307050601080704--