News for hackers. Stuff that matters.
Re:OS X BSD System Calls Reference by creshal on Wednesday July 08, 2015 @02:41AM (#9850140)
> Not being a troll here... Why would anyone care unless they are writing a libc replacement?

Statically compiling the libc is common with proprietary Linux software, if I remember correctly.

Re:OS X BSD System Calls Reference by AdieuToLogic on Wednesday July 08, 2015 @03:14AM (#9850238)
Gotcha. I guess it's an OS expectation thing then. In OS-X, it's pretty much an assumption that dynamic linking is what's going to happen (good or bad).

Thanks for clarifying this point for me.

Re:OS X BSD System Calls Reference by creshal on Wednesday July 08, 2015 @04:05AM (#9850376)
Linux userland has various libcs available (klibc, glibc, eglibc, uclibc, dietlibc, musl, …), with distributions occasionally switching between them, and ABI-incompatible changes happen every once in a while. Source-distributed software does not have to care usually, but for binary-only distribution, statically compiling the libc is the easiest bet. Thus, the kernel has to maintain compatibility.
Re:OS X BSD System Calls Reference by justincormack on Wednesday July 08, 2015 @03:46AM (#9850320)
More than that, static linking is very difficult indeed as there is not even a crt for static linking let alone libc.a, you would have to write your own.