From: Antony T Curtis <antony.t.curtis@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Running QEMU on FreeBSD
Date: Sat, 29 May 2004 22:50:56 +0100 [thread overview]
Message-ID: <1085867455.93476.10.camel@pcgem.rdg.cyberkinetica.com> (raw)
In-Reply-To: <40B902F5.30809@fabianowski.de>
On Sat, 2004-05-29 at 22:39, Bartosz Fabianowski wrote:
> > However, the problem I have is that the QEMU window does not update
> > and to see what is on the 'screen'
>
> Maybe you should give the CVS version a try. I am also running FreeBSD 5
> -CURRENT and it works beautifully for me. Actually, I have just
> installed Windows XP inside QEMU on FreeBSD. However, you will probably
> need to apply the patch I posted to the list earlier today in order to
> make the CVS version compile on FreeBSD.
Actually, I found the problem (a bit of debug code I left behind) and
QEMU is now working well :) .
I only just subscribed to the list so ... I haven't seen your patches
yet... Ho hum... duplication of effort I think... I even put in code to
use the if_tap interface, but so far it's untested.
Does the version in CVS offer much more than the 0.5.5 I downloaded and
built from?
And one of the things I am interested in doing is having a working OS/2
on my P4 laptop (OS/2 doesn't install on it) and maybe booting the XP
partition from FreeBSD.
> > The system compiler (GCC 2.95) does not understand many of the
> > constructs used in the source.
>
> I don't believe QEMU can be compiled with GCC 2.x at all. That line of
> GCC is just too broken. However, on FreeBSD 4.x you can still use the
> lang/gcc32, lang/gcc33, or lang/gcc34 port if you want to try compiling
> QEMU with GCC 3.x. Though, frankly, I don't see much point in wasting
> time on that. FreeBSD 5.x is the future ;).
Well - I have most of it compiling on FreeBSD 4.9 already... but I'm
going to try with gcc33 on 4 soon (as soon as the gcc33 port finishes
building maybe)
Thanks anyways
--
Antony T Curtis <antony.t.curtis@ntlworld.com>
next prev parent reply other threads:[~2004-05-29 21:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 21:25 [Qemu-devel] Running QEMU on FreeBSD Antony T Curtis
2004-05-29 21:39 ` Bartosz Fabianowski
2004-05-29 21:50 ` Antony T Curtis [this message]
2004-05-29 21:58 ` Bartosz Fabianowski
2004-05-29 22:09 ` Antony T Curtis
2004-05-29 22:24 ` Bartosz Fabianowski
2004-05-29 23:09 ` Antony T Curtis
2004-05-30 3:53 ` Antony T Curtis
2004-05-30 7:25 ` Markus Niemistö
2004-05-30 9:50 ` Antony T Curtis
2004-05-30 14:41 ` Bartosz Fabianowski
2004-05-30 17:27 ` Antony T Curtis
2004-05-30 18:57 ` Bartosz Fabianowski
2004-05-30 20:09 ` Antony T Curtis
2004-05-31 0:36 ` Bartosz Fabianowski
2004-05-31 1:24 ` Antony T Curtis
2004-05-31 1:42 ` Bartosz Fabianowski
2004-05-31 1:59 ` Kyle Hayes
2004-05-31 12:15 ` Bartosz Fabianowski
2004-05-31 13:22 ` Antony T Curtis
2004-05-31 9:38 ` Antony T Curtis
2004-05-31 20:36 ` Bartosz Fabianowski
2004-05-31 13:54 ` Antony T Curtis
2004-05-31 20:31 ` Bartosz Fabianowski
2004-05-31 22:15 ` Antony T Curtis
2004-05-31 22:56 ` Brion Vibber
2004-05-31 23:01 ` Bartosz Fabianowski
2004-06-02 23:18 ` qemu port (was: Re: [Qemu-devel] Running QEMU on FreeBSD) Juergen Lock
2004-06-02 23:54 ` [Qemu-devel] Re: qemu port Bartosz Fabianowski
2004-06-03 17:10 ` Gianni Tedesco
2004-06-04 18:44 ` Juergen Lock
2004-06-05 21:04 ` [Qemu-devel] FreeSBIE timer (was: Re: qemu port) Juergen Lock
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=1085867455.93476.10.camel@pcgem.rdg.cyberkinetica.com \
--to=antony.t.curtis@ntlworld.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).