From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1GeaLg-0005KA-1m
	for qemu-devel@nongnu.org; Mon, 30 Oct 2006 11:50:56 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1GeaLa-0005Iw-Ph
	for qemu-devel@nongnu.org; Mon, 30 Oct 2006 11:50:55 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1GeaLa-0005It-Kw
	for qemu-devel@nongnu.org; Mon, 30 Oct 2006 11:50:50 -0500
Received: from [65.74.133.4] (helo=mail.codesourcery.com)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1GeaLa-0002DE-J0
	for qemu-devel@nongnu.org; Mon, 30 Oct 2006 11:50:50 -0500
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] qemu vs gcc4
Date: Mon, 30 Oct 2006 16:50:46 +0000
References: <45391B22.1050608@palmsource.com>
	<200610301456.07847.paul@codesourcery.com>
	<200610301131.05721.rob@landley.net>
In-Reply-To: <200610301131.05721.rob@landley.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200610301650.46686.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Rob Landley <rob@landley.net>
Cc: qemu-devel@nongnu.org

> > > So given that one of the reasons for doing this would be getting away
> > > from depending on specific and increasily out of date versions of gcc
> > > to build the thing, what would be involved in getting this version to
> > > build under gcc-4.x?
> >
> > Should work pretty much out the box. Obviously if you build anything
> > other than m68k then all bets are off.
>
> It didn't get to "work", it broke building.  (The frighting part is that my
> patch at http://busybox.net/downloads/qemu applied to your version without
> rejects, but although that helped it get farther, it didn't finish.)
>
> I just did a standard "./configure --shutupaboutthecompilerversion; make;
> make install".  (x86 is the first target I'm interested in, as it's the
> easiest to test and you said it's using at least some of the new code...)

As I said before, the x86 target is a hybrid of the new and old code. ie. if 
it didn't work before it probably won't work after. configure 
with --target-list=m68k-user and it should work fine with gcc4.

Paul