From: "André Braga" <meianoite@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu Compile errors on OpenBSD 3.7
Date: Wed, 2 Nov 2005 23:06:09 -0200 [thread overview]
Message-ID: <2ad73a0511021706j79c7ee50hb0aeda8fad64dfb3@mail.gmail.com> (raw)
In-Reply-To: <200511021053.26132.dfeustel@verizon.net>
Same thing for FreeBSD (first the differences in IEEE FP headers, then
the vfs header, then I gave up), but since the ports build has been
patched to work around those, I refrained myself from reporting this
to the mailing list.
However, it would be really nice to have upstream QEMU building
without specific *BSD patches. Just my personal opinion, though.
--
"The weakest way to solve a problem is just to solve it"
-Alan Kay
On 11/2/05, Dave Feustel <dfeustel@verizon.net> wrote:
> 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!!!
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
next prev parent reply other threads:[~2005-11-03 1:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 15:53 [Qemu-devel] Qemu Compile errors on OpenBSD 3.7 Dave Feustel
2005-11-03 1:06 ` André Braga [this message]
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=2ad73a0511021706j79c7ee50hb0aeda8fad64dfb3@mail.gmail.com \
--to=meianoite@gmail.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).