All of lore.kernel.org
 help / color / mirror / Atom feed
* [Qemu-devel] Now for the complicated part of the OS X port...
@ 2003-10-07 10:29 qemu
  2003-10-07 12:21 ` Fabrice Bellard
  2003-10-10 17:40 ` Herbert Poetzl
  0 siblings, 2 replies; 3+ messages in thread
From: qemu @ 2003-10-07 10:29 UTC (permalink / raw)
  To: qemu-devel

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?

Mainly my objective at this point is to familiarize myself with the code,
make it all compile, then actually reimplement my changes in a way that
can be integrated into the main branch. So if anyone wonders about the
number of commented out items, such as the get_long_only function in vl,
it's because OS X doesn't have a version of that.

I have put up an updated tarball on my site:
http://www.raylucke.com/20010926/software/qemu/

Regards,

Ray

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Qemu-devel] Now for the complicated part of the OS X port...
  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
  2003-10-10 17:40 ` Herbert Poetzl
  1 sibling, 0 replies; 3+ messages in thread
From: Fabrice Bellard @ 2003-10-07 12:21 UTC (permalink / raw)
  To: qemu-devel

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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Qemu-devel] Now for the complicated part of the OS X port...
  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
@ 2003-10-10 17:40 ` Herbert Poetzl
  1 sibling, 0 replies; 3+ messages in thread
From: Herbert Poetzl @ 2003-10-10 17:40 UTC (permalink / raw)
  To: qemu; +Cc: qemu-devel

On Tue, Oct 07, 2003 at 03:29:57AM -0700, 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?
> 
> Mainly my objective at this point is to familiarize myself with the code,
> make it all compile, then actually reimplement my changes in a way that
> can be integrated into the main branch. So if anyone wonders about the
> number of commented out items, such as the get_long_only function in vl,
> it's because OS X doesn't have a version of that.
> 
> I have put up an updated tarball on my site:
> http://www.raylucke.com/20010926/software/qemu/

have a look at 

 http://developer.apple.com/documentation/DeveloperTools/Conceptual/MachORuntime/MachORuntime.pdf

HTH,
Herbert

> Regards,
> 
> Ray
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2003-10-10 17:41 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2003-10-10 17:40 ` Herbert Poetzl

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.