qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: "Andreas Färber" <afaerber@suse.de>, karl-michael.schindler@web.de
Subject: [Qemu-devel] building qemu on macos mountain lion
Date: Sat, 11 Aug 2012 15:11:37 +0100	[thread overview]
Message-ID: <CAFEAcA_A87F4o8M=Ewc+nnarkJY087YOSqhYWiTH+k_uDNgo6A@mail.gmail.com> (raw)

[Karl: I've cc'd you because I think you were the person asking about this
on #qemu IRC yesterday. Apologies if I have the wrong person...]

I just had a go at building qemu on macos X (mountain lion). The good news
is I got something working, but I had to fiddle with stuff a bit:
 * block/raw-posix.c includes IOKitLib.h -- unless we build with
  -DOS_OBJECT_USE_OBJC=0 the system headers end up trying
  to use objective C syntax and gcc barfs
 * the ui/cocoa.m file uses a system header which pulls in NSTask.h
   which uses Apple's non-standard "Blocks" objC extension. I worked
   round this by having rules.mak use clang to build all .m files (they
   don't use the major gcc-only-ism we need and they link fine with
   everything else)

[This is compiling with a fink build of mainline gcc-4.7.1]

Also 'make check' fails:

GTESTER tests/test-iov
send: Message too long
recv: Message too long
GTester: last random seed: R02Sf266e22f7524d5995dc2694b2a44c128

probably we're relying on a linuxism for sendmsg() splitting long messages,
haven't investigated yet.

I'll try to put together some patches for this but thought I'd send this
email to see if anybody else had already looked at them.

-- PMM

                 reply	other threads:[~2012-08-11 14:11 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='CAFEAcA_A87F4o8M=Ewc+nnarkJY087YOSqhYWiTH+k_uDNgo6A@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=afaerber@suse.de \
    --cc=karl-michael.schindler@web.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).