From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1InJFa-0000cl-V4
	for qemu-devel@nongnu.org; Wed, 31 Oct 2007 15:29:14 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1InJFZ-0000c3-0J
	for qemu-devel@nongnu.org; Wed, 31 Oct 2007 15:29:14 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1InJFY-0000bz-Qk
	for qemu-devel@nongnu.org; Wed, 31 Oct 2007 15:29:12 -0400
Received: from emh07.mail.saunalahti.fi ([62.142.5.117])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <holindho@cs.helsinki.fi>) id 1InJFY-00089j-C6
	for qemu-devel@nongnu.org; Wed, 31 Oct 2007 15:29:12 -0400
Message-ID: <4728D782.9060504@cs.helsinki.fi>
Date: Wed, 31 Oct 2007 21:29:06 +0200
From: Heikki Lindholm <holindho@cs.helsinki.fi>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] compiling qemu on ubuntu under parallels
References: <EDE0992A-70F7-4004-BEF5-4D12131392B5@ll.mit.edu>
	<860D57EE-925C-4DF5-8BFD-4ADE906ECDDC@ll.mit.edu>
In-Reply-To: <860D57EE-925C-4DF5-8BFD-4ADE906ECDDC@ll.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Tim Leek <tleek@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