From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1C2XTT-0005zv-Q9 for qemu-devel@nongnu.org; Wed, 01 Sep 2004 11:56:39 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1C2XTS-0005zA-4R for qemu-devel@nongnu.org; Wed, 01 Sep 2004 11:56:38 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C2XTS-0005z4-0s for qemu-devel@nongnu.org; Wed, 01 Sep 2004 11:56:38 -0400 Received: from [151.189.21.46] (helo=mail-in-01.arcor-online.net) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1C2XOG-0007di-36 for qemu-devel@nongnu.org; Wed, 01 Sep 2004 11:51:16 -0400 Received: from rz.zidlicky.org (dialin-145-254-232-027.arcor-ip.net [145.254.232.27]) by mail-in-01.arcor-online.net (Postfix) with ESMTP id 595D01C5CE for ; Wed, 1 Sep 2004 17:51:14 +0200 (CEST) Date: Wed, 1 Sep 2004 17:46:11 +0200 From: Richard Zidlicky Subject: Re: [Qemu-devel] Re: port to netbsd Message-ID: <20040901154611.GC13876@linux-m68k.org> References: <4134FC39.700@ecs.umass.edu> <87hdqjhqp1.fsf@benpfaff.org> <41353613.8080304@fastmail.fm> <41351076.4000904@gmx.com> <41354363.8060700@fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <41354363.8060700@fastmail.fm> 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 On Tue, Aug 31, 2004 at 08:34:59PM -0700, David Howland wrote: > Bochnig, Martin wrote: > > >I get exactly the same errors when trying to compile for SPARC64 (both > >Linux and Solaris10). > >Giving up. > > Looks like I'm going to aswell. > > > > >For SPARC32 it helped to use gcc 2.95 or 2.96 instead of gcc3.1/2/3x > >Curiously enough gcc3.4.1 didn't show this error. > >Install gcc2.9x into a separate location and try again. > >While you will get many more warnings and errors, it may help to fix > >that damn (hopeless) './dyngen -o op.h op.o' bugs. > > > > Sounds like a stretch... > Maybe I should wait until qemu matures a little more before I play the > porting game. Is this dyngen something that can be upgraded/replaced? no, just make sure you don't compile op.o with fomit-frame-pointer Richard