qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mateusz Loskot <mateusz@loskot.net>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Linux as VirtualBox quest OS with QEMU running Solaris
Date: Mon, 10 Jan 2011 17:59:54 +0000	[thread overview]
Message-ID: <4D2B491A.7050007@loskot.net> (raw)
In-Reply-To: <4D2B3D02.2000104@mail.berlios.de>

On 10/01/11 17:08, Stefan Weil wrote:
> Am 10.01.2011 12:19, schrieb Mateusz Loskot:
>> On 07/01/11 18:15, Stefan Weil wrote:
>>> There are no precompiled windows binaries of current qemu,
>>> so you will have to compile them yourself (which is not difficult
>>> once you have the correct mingw environment).
>>
>> Great. I think I should be able to do that.
>>
>> Which version of QEMU source code should I grab?
>> Latest stable or development version from Git repo?
>
>
> I suggest using QEMU git master. You could try the binaries
> from my website: http://www.weilnetz.de/qemu/

Stefan,

Thank you very much!
So far, I have tried to use versions of QEMU from Qemu Manager 0.7
as well as QEMU 0.13 from
http://homepage3.nifty.com/takeda-toshiya/
but without any luck. I suppose it's because these versions do not
have most recent OpenBIOS usable with SPARC.

I quickly tried your binaries and it looks I have to run them from 
within MSYS environment, isn't it?
I'm getting runtime error reporting msys-z.dll is missing.


I tried to find instructions on building QEMU with MinGW.
No luck. Is there anything available?

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Member of ACCU, http://accu.org

  reply	other threads:[~2011-01-10 18:07 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07 17:28 [Qemu-devel] Linux as VirtualBox quest OS with QEMU running Solaris Mateusz Loskot
2011-01-07 17:36 ` Michal Suchanek
2011-01-10 11:17   ` Mateusz Loskot
2011-01-07 18:15 ` Stefan Weil
2011-01-10 11:19   ` Mateusz Loskot
2011-01-10 17:08     ` Stefan Weil
2011-01-10 17:59       ` Mateusz Loskot [this message]
2011-01-10 21:04         ` Artyom Tarasenko
2011-01-12 11:47           ` Mateusz Loskot
2011-01-12 11:57             ` Artyom Tarasenko
2011-01-12 12:32               ` Mateusz Loskot
2011-01-12 14:28                 ` Mateusz Loskot
2011-01-12 14:40                   ` Artyom Tarasenko
2011-01-12 15:21                     ` Mateusz Loskot
2011-01-12 16:48                       ` Michal Suchanek
2011-01-12 17:15                         ` Mateusz Loskot
2011-01-12 19:00                           ` Blue Swirl
2011-01-12 23:34                           ` Mateusz Loskot
2011-01-13 10:13                             ` Michal Suchanek
2011-01-13 12:40                               ` Mateusz Loskot
2011-01-13 16:01                                 ` Mateusz Loskot
2011-01-10 22:18         ` Stefan Weil
2011-01-12 11:38           ` Mateusz Loskot
2011-01-12 12:30             ` Mateusz Loskot
2011-01-12 19:05               ` Stefan Weil
2011-01-12 19:17                 ` Stefan Weil
2011-01-12 21:37                   ` Michal Suchanek
2011-01-12 21:46                     ` Stefan Weil
2011-01-07 20:37 ` Blue Swirl
2011-01-10 11:22   ` Mateusz Loskot
2011-01-13 15:32 ` [Qemu-devel] " Mateusz Loskot

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=4D2B491A.7050007@loskot.net \
    --to=mateusz@loskot.net \
    --cc=qemu-devel@nongnu.org \
    --cc=weil@mail.berlios.de \
    /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).