Re: [go-nuts] Alternative way of setting cgocheck=0

2017-11-16 Thread Ian Lance Taylor
On Thu, Nov 16, 2017 at 9:46 AM, Srimanth Gunturi wrote: > > My environment is unable to accept this format due to the double '=' in the > same key/value. That's really odd. > Is there an alternate way of expressing the same environment variable - like > 'GODEBUG=cgocheck:0' or something like th

Re: [go-nuts] Alternative way of setting cgocheck=0

2017-11-16 Thread 'Srimanth Gunturi' via golang-nuts
My environment is unable to accept this format due to the double '=' in the same key/value. Is there an alternate way of expressing the same environment variable - like 'GODEBUG=cgocheck:0' or something like that? On Wed, Nov 15, 2017 at 9:05 PM, Ian Lance Taylor wrote: > On Wed, Nov 15, 2017

Re: [go-nuts] Alternative way of setting cgocheck=0

2017-11-15 Thread Ian Lance Taylor
On Wed, Nov 15, 2017 at 9:03 PM, 'SrimanthG' via golang-nuts wrote: > > Is there any programmatic way of disabling cgo runtime checks? > > The documentation says to set environment variable "GODEBUG=cgocheck=0". > However, this does not work for me as I do not control the environment. > Hoping the

[go-nuts] Alternative way of setting cgocheck=0

2017-11-15 Thread 'SrimanthG' via golang-nuts
Hello, Is there any programmatic way of disabling cgo runtime checks? The documentation says to set environment variable "GODEBUG=cgocheck=0". However, this does not work for me as I do not control the environment. Hoping there is a programmatic way for disabling the runtime checks? Regards, Sr