From: Dave Feustel <dfeustel@verizon.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Qemu Compile errors on OpenBSD 3.7
Date: Wed, 02 Nov 2005 10:53:25 -0500 [thread overview]
Message-ID: <200511021053.26132.dfeustel@verizon.net> (raw)
There occur a number of compile errors when I
attempt to build Qemu on OpenBSD 3.7 using gcc 3.3.5.
Symbols FE_RN, FE_RM, etc are undefined. They are used
After I fixed that I got a number of other errors which I have
not yet had time to figure out. Qemu has been ported to
OpenBSD, but I wanted to get the latest version and possibly
start hacking on it.
Thanks,
Dave Feustel
--
Tired of having to defend against Malware?
You know: trojans, viruses, SPYWARE, ADWARE,
KEYLOGGERS, rootkits, worms and popups.
Then Switch to OpenBSD with a KDE desktop!!!
next reply other threads:[~2005-11-02 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 15:53 Dave Feustel [this message]
2005-11-03 1:06 ` [Qemu-devel] Qemu Compile errors on OpenBSD 3.7 André Braga
2005-11-03 10:01 ` Dave Feustel
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=200511021053.26132.dfeustel@verizon.net \
--to=dfeustel@verizon.net \
--cc=dfeustel@mindspring.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).