From: Damien Mascord <tusker@tusker.org>
To: jplatte@naasa.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-system-sparc on windows
Date: Sun, 22 May 2005 00:14:26 +0800 [thread overview]
Message-ID: <428F5E62.7010808@tusker.org> (raw)
In-Reply-To: <200505201718.52326.jplatte@naasa.net>
Joerg Platte wrote:
>Hi!
>
>
<snip/>
>Now qemu starts but crashes just after opening its window. This does not
>happen to the precompiled version from
>http://www.freeoszoo.org/ftp/qemu/win32/daily/, but this version does not
>boot linux either. It semms to get stuck in an endless loop...
>
>Now I have two questions:
>Why does my compiled version crash? Did I forget something during the build
>process?
>
To answer one of your questions,
You are probably using GCC 3.4 for mingw rather than GCC 3.3.
Try the 3.3 toolset, and see how you fare :)
Damien
next prev parent reply other threads:[~2005-05-21 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 15:18 [Qemu-devel] qemu-system-sparc on windows Joerg Platte
2005-05-21 16:14 ` Damien Mascord [this message]
2005-05-23 6:55 ` Joerg Platte
2005-05-23 7:24 ` Joerg Platte
2005-05-23 14:25 ` Joerg Platte
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=428F5E62.7010808@tusker.org \
--to=tusker@tusker.org \
--cc=jplatte@naasa.net \
--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).