qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org, Brad <brad@comstyle.com>
Subject: Re: [Qemu-devel] QEMU TCG code does not build with OpenBSD PowerPC
Date: Mon, 11 May 2009 18:30:09 +0300	[thread overview]
Message-ID: <f43fc5580905110830u776eb768q441637b958a6a1ab@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0905110125560.2330@linmac.oyster.ru>

On 5/11/09, malc <av1474@comtv.ru> wrote:
> On Sun, 10 May 2009, Brad wrote:
>
>  > On Sunday 10 May 2009 14:41:13 malc wrote:
>  > > On Sat, 9 May 2009, Brad wrote:
>  > > > On Sat, Apr 11, 2009 at 10:58:06AM +0400, malc wrote:
>  > > > > On Fri, 10 Apr 2009, Brad wrote:
>
>
> [..snip..]
>
>
>  > >
>  > > You tested this and it works?
>  >
>  > Its a moot point if it "works" since QEMU 0.10.x is broken on all archs
>  > we had working with 0.9.x and QEMU 0.10.x is far from building as is.
>  >
>  > So my first priority is to get it to even build properly on the archs we
>  > supported with our 0.9.x port (amd64 i386 powerpc).
>  >
>
>
> I see. I was under impression that Blue Swirl was building it successfully
>  on (at least) OpenBSD not so long ago. How is it broken?

QEMU works on OpenBSD/Sparc64 (at least sparc-softmmu is fine, other
targets I tested do not work well), and OpenBSD/Sparc32 did build at
some point. I had problems installing OpenBSD/i386 under QEMU, so I
haven't tested that.

  reply	other threads:[~2009-05-11 15:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-10 12:21 [Qemu-devel] QEMU TCG code does not build with OpenBSD PowerPC Brad
2009-04-10 12:39 ` Andreas Färber
2009-04-11  6:58 ` malc
2009-05-10  2:12   ` Brad
2009-05-10 18:41     ` malc
2009-05-10 19:00       ` Brad
2009-05-10 21:27         ` malc
2009-05-11 15:30           ` Blue Swirl [this message]
2009-05-11 16:59             ` Brad
2009-05-11 18:00               ` Andreas Färber
2009-05-11 18:20               ` Blue Swirl
2009-05-11  1:46       ` M. Warner Losh

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=f43fc5580905110830u776eb768q441637b958a6a1ab@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=av1474@comtv.ru \
    --cc=brad@comstyle.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).