Until recently some functions in the os/user package were only available via glibc.
The net package links to cgo by default to pick up the nss libraries, which are important if your installation uses ldap. I argued that this should not be the default in the 1.5 release, that most users deploying on Linux expected a static binary by default, however my arguments were not sufficiently convincing. The tldr is rationale for the linking behaviour of a go binary is implantation defined, and the go authors choose to make their implementation use cgo where available. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
