docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp golang:1.6 go buildYou 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
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thank You
To unsubscribe from this group and all its topics, send an email to golang-nuts...@googlegroups.com.
$ eval "$(gimme 1.8beta2)"
The easy solution here is gimme.$ eval "$(gimme 1.8beta2)"Downloads and installs go and sets all the environment variables for you.
On Wednesday, December 14, 2016 at 11:58:55 AM UTC-5, aind...@gmail.com wrote:I currently have the distribution "go version go1.7.1 darwin/amd64" installed. However, I'd like to test my applications on the 1.8 beta.
- Is it okay to install another distribution without messing up the environment variables?
- If I build from source, can I scope the installation to a specific directory?
- What is the recommended procedure for having multiple installations side-by-side?
Thank You,Akhil Indurti
--
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+unsubscribe@googlegroups.com.