From: Dave Feustel <dfeustel@verizon.net>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu bug when building for OpenBSD
Date: Mon, 14 Nov 2005 18:13:35 -0500 [thread overview]
Message-ID: <200511141813.35358.dfeustel@verizon.net> (raw)
In-Reply-To: <200511142205.52610.paul@codesourcery.com>
On Monday 14 November 2005 17:05, Paul Brook wrote:
> On Monday 14 November 2005 21:53, Dave Feustel wrote:
> > When I try to build qemu 7.2 for OpenBSD, I get a file
> > not found error for libutil.h in vl.c. This should not
> > happen since there is no libutil.h in OpenBSD. Has
> > this been fixed yet? (or can someone point me to
> > a copy of libutil.h and its library source)?
>
> Have you tried not including it? Or including util.h instead?
> google suggests it's usually used for openpty(), but that bit of code is
> disabled on bsd anyway.
I tried commenting out the #include line and got by that problem.
I got another error relating to undefined symbol INT16_MAX.
Then I put all the qemu source into an svn repository to begin editing
it, but, upon checkout ran into a problem with links due to altered
source tree structure, about which I just posted.
Dave
> Paul
>
--
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!!!
NOW with Virtual PC OS support via QEMU!
next prev parent reply other threads:[~2005-11-14 23:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 21:53 [Qemu-devel] Qemu bug when building for OpenBSD Dave Feustel
2005-11-14 22:05 ` Paul Brook
2005-11-14 23:13 ` Dave Feustel [this message]
2005-11-14 23:20 ` Paul Brook
2005-11-15 10:41 ` [Qemu-devel] why run qemu not use sudo, the /etc/qemu-ifup will not run swz
2005-11-15 14:31 ` hmm
2005-11-16 3:02 ` swz
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=200511141813.35358.dfeustel@verizon.net \
--to=dfeustel@verizon.net \
--cc=dfeustel@mindspring.com \
--cc=paul@codesourcery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.