On Tue, Aug 9, 2016 at 1:38 AM, Seb Binet wrote:
>
>
> On Mon, Aug 8, 2016 at 5:12 PM, Ian Lance Taylor wrote:
>>
>> On Sun, Aug 7, 2016 at 7:08 PM, Amit Saha wrote:
>> >
>> > From an old thread [1], I learned that CGO_ENABLED=0 will create static
>> > binaries for programs using the net/http pa
On Mon, Aug 8, 2016 at 5:12 PM, Ian Lance Taylor wrote:
> On Sun, Aug 7, 2016 at 7:08 PM, Amit Saha wrote:
> >
> > From an old thread [1], I learned that CGO_ENABLED=0 will create static
> > binaries for programs using the net/http package. I still see the same
> > behavior as of go version go1.
On Sun, Aug 7, 2016 at 7:08 PM, Amit Saha wrote:
>
> From an old thread [1], I learned that CGO_ENABLED=0 will create static
> binaries for programs using the net/http package. I still see the same
> behavior as of go version go1.6.3 linux/amd64. Does this mean this is the
> only way to get static
Hi all,
>From an old thread [1], I learned that CGO_ENABLED=0 will create static
binaries for programs using the net/http package. I still see the same
behavior as of go version go1.6.3 linux/amd64. Does this mean this is the
only way to get statically linked binaries for programs using net/htt