Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: generating mach-o executable files by hand

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: generating mach-o executable files by hand

Subject: Re: generating mach-o executable files by hand
From: Jean-Daniel Dupas <email@hidden>
Date: Wed, 7 Jan 2009 11:11:22 +0100


Le 7 janv. 09 à 10:24, Joel Reymont a écrit :

Terry,
On Jan 7, 2009, at 3:33 AM, Terry Lambert wrote:
You have to use at least *a* linker; if you don't, you won't be able to import the system call stubs from libc/libsystem
I hope to prove you wrong, shortly. This is a Forth so all I need is stubs for dlopen, dlclose, dlsym and dlerror. I also need to jump to an entry point. This works fine on Linux with the ELF format.

Thanks, Joel


FWIW, the OS X linker is open source:

	http://www.opensource.apple.com/darwinsource/DevToolsOct2008/ld64-85.2.1

But I would recommand generating mach-o objects, and link them using Apple ld.


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



References:  
  >generating mach-o executable files by hand (From: Joel Reymont <email@hidden>)
  >Re: generating mach-o executable files by hand (From: Terry Lambert <email@hidden>)
  >Re: generating mach-o executable files by hand (From: Joel Reymont <email@hidden>)




Prev by Date:
Re: generating mach-o executable files by hand

Next by Date:
Descriptor Passing Mac OS X 10.5.4 ( X86_64 )

Previous by thread:
Re: generating mach-o executable files by hand

Next by thread:
Re: generating mach-o executable files by hand

Index(es):

Date
Thread