All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice.bellard@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Now for the complicated part of the OS X port...
Date: Tue, 07 Oct 2003 14:21:48 +0200	[thread overview]
Message-ID: <3F82AFDC.1040004@free.fr> (raw)
In-Reply-To: 61775.67.168.46.137.1065522597.squirrel@mail.apvio.net

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.

  reply	other threads:[~2003-10-07 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 10:29 [Qemu-devel] Now for the complicated part of the OS X port qemu
2003-10-07 12:21 ` Fabrice Bellard [this message]
2003-10-10 17:40 ` Herbert Poetzl

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=3F82AFDC.1040004@free.fr \
    --to=fabrice.bellard@free.fr \
    --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 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.