Creating static Mac OS X C build

by

It is not supported in Mac OS X’s gcc:

http://discussions.apple.com/message.jspa?messageID=11053384

Perhaps that “-static” flag flat out won’t work on MacOS X. Not all features of gcc are implemented on MacOS X. Apple won’t even be using gcc in future versions of the OS.

I don’t know how to link using “-static”. I can’t think of any reason to do so on MacOSX. If I knew why you wanted to use “-static” I might be more interested in the problem. Right now, I just don’t get it. By asking for help, you are essentially asking for collaborators on the project – even if it is only for 10 minutes. You need to get me interested.

And http://developer.apple.com/library/mac/#qa/qa2001/qa1118.html

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.

Update: The prohibited is a static binary. But you still can compile some static library and use it with you another program. Program will be linked statically with your library, but other libraries like libc will be dynamic, so program will be a dynamic executable.

More Related Contents:

  1. Can’t compile C program on a Mac after upgrade to Mojave
  2. Can’t compile a C program on a Mac after upgrading to Catalina 10.15
  3. Can I mix static and shared-object libraries when linking?
  4. GCC left shift overflow
  5. Why can’t the size of a static array be made variable?
  6. Compiling a C program that uses OpenGl in Mac OS X
  7. Removing trailing newline character from fgets() input
  8. C undefined behavior. Strict aliasing rule, or incorrect alignment? [duplicate]
  9. Order of local variable allocation on the stack
  10. Undefined reference to `pow’ and `floor’
  11. Adding leading underscores to assembly symbols with GCC on Win32?
  12. What is the difference between C, C99, ANSI C and GNU C?
  13. Why didn’t gcc (or glibc) implement _s functions?
  14. What’s the difference between static inline, extern inline and a normal inline function?
  15. How to check if a given file descriptor stored in a variable is still valid?
  16. How to get network adapter stats in linux/Mac OSX?
  17. How can I multiply 64 bit operands and get 128 bit result portably?
  18. Why does gcc allow arguments to be passed to a function defined to be with no arguments?
  19. Check glibc version for a particular gcc compiler
  20. Why we need Clobbered registers list in Inline Assembly?
  21. What is “…” in switch-case in C code
  22. How are static variables with the same name in different functions identified by the System?
  23. C code with undefined results, compiler generates invalid code (with -O3)
  24. Compiler changes printf to puts
  25. How to get the size of a C function from inside a C program or with inline assembly?
  26. Why is execstack required to execute code on the heap?
  27. gcc detect duplicate symbols/functions in static libraries
  28. Why won’t extern link to a static variable?
  29. Order of fields when using a bit field in C
  30. How much overhead can the -fPIC flag add?

Leave a Comment