You never need to set GOROOT and setting GOROOT will bring you confusing problems to debug in the future.
On Friday, 16 December 2016 11:24:20 UTC+11, Akhil Indurti wrote: > > Yeah, I don't set $GOROOT, but $GOROOT_BOOTSTRAP in order to compile. > > Symlinking might be a good idea for convenience, but can I use my > system-wide $GOPATH to test my src, or do I duplicate that as well. > > Thank You > > > On Dec 15, 2016 4:54 PM, "Dave Cheney" <da...@cheney.net <javascript:>> > wrote: > > You can build as many different versions of Go as you need by checking the > source out into different locations and running the src/make.bash script. > > You should not set GOROOT, building from source will encode the correct > location into the bin/go tool during the process. > > To make life simpler for yourself, add a symlink to the various versions > of the go tool you have built, eg. > > ln -s $HOME/go1.6/bin/go $HOME/bin/go1.6 > > Dave > > -- > You received this message because you are subscribed to a topic in the > Google Groups "golang-nuts" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/golang-nuts/uqns15dYvDI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > golang-nuts...@googlegroups.com <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > -- 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.
