From: malc <av1474@comtv.ru>
To: "J. B. Rainsberger" <jbrainsberger@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Building from HEAD on Mac OS 10.6.1: second compile error
Date: Wed, 16 Sep 2009 15:09:24 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0909161507230.15704@linmac.oyster.ru> (raw)
In-Reply-To: <f12373d0909160346s3ec0cbbcu59dfd1b3688fe5d9@mail.gmail.com>
On Wed, 16 Sep 2009, J. B. Rainsberger wrote:
> Hello, folks.
>
> Thanks for your help so far. I have run into a second build failure. I
> need your help. I hope this snippet gives you enough context, and if
> not, tell me and I'll attach entire build logs.
Darwin-user is unmaintained and bitrotted to the point of being broken
entirely. You'd be better of configuring only those targets you are
intested in, for example:
./configure --target-list=i386-softmmu,mips-softmmu
[..snip..]
--
mailto:av1474@comtv.ru
prev parent reply other threads:[~2009-09-16 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 10:46 [Qemu-devel] Building from HEAD on Mac OS 10.6.1: second compile error J. B. Rainsberger
2009-09-16 11:09 ` malc [this message]
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=Pine.LNX.4.64.0909161507230.15704@linmac.oyster.ru \
--to=av1474@comtv.ru \
--cc=jbrainsberger@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).