site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com User-agent: Internet Messaging Program (IMP) H3 (4.3.4) Hello, ld64 for Mac OS X 10.4 and 10.5 can be built fine by people outside Apple. Thanks, Jonas ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... The one for 10.6 fails to build (on 10.6) because a) mach-o/arm/* is missing (I guess I can copy this from an iPhone SDK) b) libunwind/* is missing (from the errors, it seems as these files should be part of the ld64 project, but they aren't). The relevant files appear to be libunwind/DwarfInstructions.hpp, libunwind/AddressSpace.hpp and libunwind/Registers.hpp I'd like to debug it, because it has a problem dealing with routines identified by multiple global symbols if these routines are indirectly reachable from a mod_init/mod_term routine (when moving such code around, ld only moves around the associated symbols that are referred to in the current object file rather than all of them, resulting in random code execution if one of the other symbols is referred from another object file -- yes, I will file a bug report for this). It seems that I can work around the ld bug for the init routines by specifying -no_order_inits, but it doesn't help for the mod_term ones (even though ld does not explicitly reorder them at first sight). If I can debug ld, maybe I can find a workaround for the mod_term routines as well. So can someone give me some hints on where I can find the libunwind and the mach-o/arm files? This email sent to site_archiver@lists.apple.com