From: John Coiner <jcoiner@stanfordalumni.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [patch] fix for broken build due to nonblocking IO
Date: Tue, 04 Oct 2005 22:21:15 -0400 [thread overview]
Message-ID: <4343389B.8040500@stanfordalumni.org> (raw)
Here are two new patches, which attempt to fix the QEMU build for the
dependency on pthreads introduced by nonblocking IO. They are on the
nonblocking IO page:
http://people.brandeis.edu/~jcoiner/qemu_idedma/qemu_dma_patch.html#install
The first is a quick fix to the QEMU's 'configure' script and
'Makefile.target'. On most unixes this will fix the build.
On MinGW, the patch makes the configure script assume that the pthreads
headers and DLL live in certain locations. The second patch (for MinGW
only) applies to the pthreads-w32 distribution, so that it puts those
headers and that DLL into those certain locations when you run 'make
install'.
The MinGW stuff here is pretty lame. It may not be better than nothing,
but I don't really know what the right way is. That's why the build
patches are separate from the C code patches -- they may be going down
the wrong path, especially on MinGW.
-- John
reply other threads:[~2005-10-05 2:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4343389B.8040500@stanfordalumni.org \
--to=jcoiner@stanfordalumni.org \
--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).