[go-nuts] who does go compiler link executable to glibc without an apparent reason?

2017-11-07 Thread Dave Cheney
The net and os/user packages will force dynamic linking unless CGO_ENABLED=0 or you are cross compiling. -- 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-

Re: [go-nuts] who does go compiler link executable to glibc without an apparent reason?

2017-11-05 Thread Jan Mercl
Using some of the net/... package calls libc unless disabled. On Sun, Nov 5, 2017, 17:13 Howard Guo wrote: > Hello fellow gophers. > > I've a small number of go programs that only use standard library > functions without any 3rd party library dependency. A strange behaviour was > observed during

[go-nuts] who does go compiler link executable to glibc without an apparent reason?

2017-11-05 Thread Howard Guo
Hello fellow gophers. I've a small number of go programs that only use standard library functions without any 3rd party library dependency. A strange behaviour was observed during compilation (go build) - most of them compile into static executable, but few of them end up linking to glibc. With