From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24)
	id 1A6qrC-0005IB-5Q
	for qemu-devel@nongnu.org; Tue, 07 Oct 2003 08:22:26 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24)
	id 1A6qqf-0005Cn-Ay
	for qemu-devel@nongnu.org; Tue, 07 Oct 2003 08:22:24 -0400
Received: from [213.41.78.25] (helo=smtp-ft1.fr.colt.net)
	by monty-python.gnu.org with esmtp (Exim 4.24) id 1A6qqc-0005BG-IK
	for qemu-devel@nongnu.org; Tue, 07 Oct 2003 08:21:50 -0400
Received: from alcor.imaginet.fr (alcor.imaginet.fr [195.68.86.12])
	by smtp-ft1.fr.colt.net with ESMTP id h97CLnM04230
	for <qemu-devel@nongnu.org>; Tue, 7 Oct 2003 14:21:49 +0200
Received: from gw.netgem.com ([195.68.2.34]:64934 helo=free.fr)
	by alcor.imaginet.fr with esmtp (Exim) id 1A6qsh-0002Hd-N5
	for <qemu-devel@nongnu.org>; Tue, 07 Oct 2003 14:23:59 +0200
Message-ID: <3F82AFDC.1040004@free.fr>
Date: Tue, 07 Oct 2003 14:21:48 +0200
From: Fabrice Bellard <fabrice.bellard@free.fr>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Now for the complicated part of the OS X port...
References: <61775.67.168.46.137.1065522597.squirrel@mail.apvio.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.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://mail.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

qemu@raylucke.com wrote:
> I am able to get every file, including vm86.o,  op-i386.o, helper-i386.o,
> etc. to compile (after quite a few code mods that disable certain
> functionality) except the syscall.c file, but that's because it is made
> specifically for Linux, and Darwin will need it's own, which is a job in
> itself. The other files that don't compile are those that include the
> dyngen-generated includes.
> 
> I am wondering if anyone on this list knows much about the Mach-O file
> format, and would possibly consider writing a dyngen program that will
> generate the appropriate headers so this thing will compile the rest the
> way.
> 
> If not, Fabrice, do you have any pointers of where I can get a crash
> course on writing a dyngen program for Mach-O files so I can let it
> process Darwin's applicable files?

The best source of information seems to be the binutils source code (in 
particular the BFD library patched by Apple). Then it is possible to 
patch dyngen to support the Mach-O format or to write a Mach-O to ELF 
object file converter.

Fabrice.