cooch wrote:In principle, the same approach should work under OS/X (but basic lack of access to an OS/X-based machine that I can 'futz' with limits anything further there).
OK, managed to lay my hands on a very new Mac -- installed all the dev tools (Xcode, gcc, gfortran and all that), loaded up the MARK source, and compiled a dynamically linked version with no problems.
However, when I tried to compile a statically linked version (as per discussions earlier in this thread), crashed and burned. After much fooling, and talking to some high-end Mac types, I learned the following (right from the folks in Cupertino):
Static linking of user binaries is not supported on Mac OS X. Tying user binaries to the internal implementation of Mac OS X libraries and interfaces would limit our ability to update and enhance Mac OS X. Instead, dynamic linking is supported (linking against crt1.o automatically instead of looking for crt0.o, for example).
We strongly recommend that you consider the limitations of statically linking very carefully, and consider your customer and their needs, plus the long-term support you will need to provide.
So there you have it. The folks at Apple have decided that since a statically linked binary that works *today* might not work *tomorrow* -- say, following an OS/X update, and since anything that doesn't work would 'degrade from the users experience', they flatly don't let you do it.
Which leaves me with 3 conclusions:
1\ even post-Jobs Apple is still anal compulsive when it comes to 'locking things down'
2\ even after considering the 'limitations of statically linking' (as per their missive), it isn't even clear that it is possible at all. Whereas it is possible, and (as it turns out) straightforward on Windows, GNU/Linux, Unix, Solaris....
3\ so, no statically linked MARK executable for OS/X people. Meaning (going back to the beginning), if you can get things working with the dynamically linked version of MARK, then....great! If not, you're either 'out of luck', or destined to spend some quality time figuring out how to change (typically) paths to various libraries under OS/X. If you manage to figure it out, please post the steps you took, so that others (including me) can benefit from your experiences (and not have to spin their wheels reinventing the wheel...). Or, if there is someone out there who knows the obscure (i.e., not obvious) steps I'd need to do to do a static linking under OS/X, I'll buy you a virtual beer of your choice.
Either that, or [rant] invest in a computer with an operating system that actually lets you (the person who forked over the money) do whatever you want with it...[/rant]