All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Zidlicky <rz@linux-m68k.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: port to netbsd
Date: Wed, 1 Sep 2004 17:46:11 +0200	[thread overview]
Message-ID: <20040901154611.GC13876@linux-m68k.org> (raw)
In-Reply-To: <41354363.8060700@fastmail.fm>

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

  parent reply	other threads:[~2004-09-01 15:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31 22:31 [Qemu-devel] port to netbsd (was: FreeBSD != *BSD) David Howland
2004-08-31 22:45 ` [Qemu-devel] Re: port to netbsd Ben Pfaff
2004-09-01  2:38   ` David Howland
2004-08-31 23:44     ` Paul Brook
2004-09-01  3:27       ` David Howland
2004-08-31 23:57     ` Bochnig, Martin
2004-09-01  3:34       ` David Howland
2004-09-01 14:38         ` Bochnig, Martin
2004-09-01 14:45           ` David Howland
2004-09-01 15:46         ` Richard Zidlicky [this message]
2004-08-31 23:58     ` Bochnig, Martin
2004-09-01  5:23 ` [Qemu-devel] " David Howland
2004-09-01  3:25   ` Bochnig, Martin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040901154611.GC13876@linux-m68k.org \
    --to=rz@linux-m68k.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.