All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heikki Lindholm <holindho@cs.helsinki.fi>
To: qemu-devel@nongnu.org
Cc: Tim Leek <tleek@ll.mit.edu>
Subject: Re: [Qemu-devel] compiling qemu on ubuntu under parallels
Date: Wed, 31 Oct 2007 21:29:06 +0200	[thread overview]
Message-ID: <4728D782.9060504@cs.helsinki.fi> (raw)
In-Reply-To: <860D57EE-925C-4DF5-8BFD-4ADE906ECDDC@ll.mit.edu>

Tim Leek kirjoitti:
> Okay I'm having another go at you folk.  Again, please feel free to 
> shunt me off in the proper direction when I get annoying.
> 
> According to Andreas, intel macs can't compile the QEMU source as-is.  
> I'd need to use Q which only works because it has been patched 
> to accommodate gcc-4.  I've tried this and it works.  A script applies a 
> bunch of patches and the resulting Q app works properly.  
> 
> But I am a little worried about working with a forked source tree.  We 
> are building instrumentation for computer security research that will 
> sit on top of QEMU.  Thus, we'd like to have it as close and compatible 
> as possible to the original QEMU source.  

What exactly is the problem building a darwin x86 gcc-3.4? I have built 
a darwin gcc x86 cross-compiler on a ppc host, which seems to create 
sane-looking executables, but have no intel mac, so...

-- Heikki Lindholm

  reply	other threads:[~2007-10-31 19:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <EDE0992A-70F7-4004-BEF5-4D12131392B5@ll.mit.edu>
2007-10-31 19:13 ` [Qemu-devel] compiling qemu on ubuntu under parallels Tim Leek
2007-10-31 19:29   ` Heikki Lindholm [this message]
2007-10-31 19:42     ` Tim Leek
2007-10-31 20:06       ` andrzej zaborowski
2007-10-31 20:37         ` Tim Leek
2007-11-05 23:53           ` Weissmann Markus

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=4728D782.9060504@cs.helsinki.fi \
    --to=holindho@cs.helsinki.fi \
    --cc=qemu-devel@nongnu.org \
    --cc=tleek@ll.mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.