A personal work journal

go on Mac makes static binaries!

I’ve complained a bunch about how MacOS doesn’t let you compile static binaries; you absolutely must dynamically link libc.

go doesn’t have that problem. go doesn’t use libc. The binaries “go build” creates appear to be truly statically linked, at least according to “otool -L”. Although apparently there’s another compiler “gccgo” that does link with glibc, or else I misunderstand.

Bonus fact: if you strip a Mac go binary, it segfaults when you run it.