From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, hausen@punkt.de
Subject: Re: [Qemu-devel] All the world's a VAX! - reloaded
Date: Wed, 09 May 2007 14:35:10 -0600 (MDT) [thread overview]
Message-ID: <20070509.143510.-233671979.imp@bsdimp.com> (raw)
In-Reply-To: <20070509194920.GA50127@hugo10.ka.punkt.de>
In message: <20070509194920.GA50127@hugo10.ka.punkt.de>
"Patrick M. Hausen" <hausen@punkt.de> writes:
: P.S. No, I don't have a patch, because what I did locally does
: not fix the problem. Once we change
:
: #if defined(__linux__)
: to
: #if defined(__linux__) || defined(__DARWIN__)
:
: we will in no time have to add
:
: || defined(__FreeBSD__)
: ...
: ...
#ifdef unix
...
#endif
is the traditional way to say this :-)
Warner
next prev parent reply other threads:[~2007-05-09 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 19:49 [Qemu-devel] All the world's a VAX! - reloaded Patrick M. Hausen
2007-05-09 20:35 ` M. Warner Losh [this message]
2007-05-09 22:07 ` Johannes Schindelin
2007-05-11 3:55 ` Carlos A. M. dos Santos
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=20070509.143510.-233671979.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=hausen@punkt.de \
--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).