From: David Coppa <dcoppa@gmail.com>
To: dfeustel@mindspring.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Missing ENOTSUP def for OpenBSD
Date: Sun, 27 Nov 2005 16:23:45 +0100 [thread overview]
Message-ID: <a6e8c9420511270723l4a99e125rb7e0bb762a1bc0df@mail.gmail.com> (raw)
In-Reply-To: <200511270938.49098.dfeustel@verizon.net>
Hi Dave,
take a look at these (unofficial) ports:
http://todd.fries.net/ports/qemu-0.7.0.tgz
http://todd.fries.net/ports/qemu-0.7.1.tgz
http://todd.fries.net/ports/qemu-20050427.tgz
A lot of patches need to be applied in order to have a working qemu on OpenBSD:
$ ls -1 qemu/patches/
patch-Makefile
patch-Makefile_target
patch-audio_audio_c
patch-audio_ossaudio_c
patch-configure
patch-dis-asm_h
patch-dyngen-exec_h
patch-exec_c
patch-fpu_softfloat-native_c
patch-fpu_softfloat-native_h
patch-gnu-c99-math_h
patch-hw_pc_c
patch-hw_pcnet_c
patch-hw_pcnet_h
patch-osdep_h
patch-slirp_slirp_config_h
patch-target-arm_cpu_h
patch-target-i386_cpu_h
patch-target-ppc_cpu_h
patch-target-ppc_op_helper_c
patch-target-sparc_cpu_h
patch-vl_c
patch-vl_h
patch-x_keymap_c
$ grep ENOTSUP qemu/patches/*
qemu/patches/patch-configure:+ echo "#define ENOTSUP 4096" >> $config_h
Regards,
David
On 11/27/05, Dave Feustel <dfeustel@verizon.net> wrote:
> When I attempt to build qemu from CVS on OpenbSD 3.7
> using gcc 3.3.5 (propolice), ENOTSUP is reported as an
> undefined symbol. ENOTSUP is defined in vl.h, but it is
> only defined for Win32. Could a #define OPENBSD
> be added to qemu source for building qemu on OpenBSD
> platforms?
>
> Thanks,
> Dave Feustel
next prev parent reply other threads:[~2005-11-27 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-27 14:38 [Qemu-devel] Missing ENOTSUP def for OpenBSD Dave Feustel
2005-11-27 15:23 ` David Coppa [this message]
2005-11-27 18:24 ` Dave Feustel
2005-11-28 8:46 ` David Coppa
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=a6e8c9420511270723l4a99e125rb7e0bb762a1bc0df@mail.gmail.com \
--to=dcoppa@gmail.com \
--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).