Go Linux installation notes, record the pits encountered

This is a creation in Article, where the information may have evolved or changed.

Since ECUG2013, I want to get in touch with go early.

Listen, Xu Xiwei and Xie Mengjun's speech.

Discover that the Go Network library is indeed very powerful, high load weapon, some of the language of the simplification resulting in easy to write efficient code, and development efficiency is very high , should be very high . (Rpcjson,xml,..... Some of the other libraries are also very mature)

is not the legend of the good stuff, you have to use their own to know

So start tasting go: D

PS This article is completely rookie study posts

ECUG Video Transmission

Www.youtube.com/watch?v=af7qOeN9Mvk

The above 2 people's books are very good learning materials, of course, the means to go is also very good

"Go Web Programming" https://github.com/astaxie/build-web-application-with-golang/

Environment:

$LSB _release-a

Ubuntu 12.04.3 LTS

$uname-A (or $cat/proc/version)

Linux 3.8.0-33-generic gcc version 4.6.3

2 Types of mounting options

1. Https://code.google.com/p/go/downloads/list

Download go1.2.linux-amd64.tar.gz directly

Decompression command TAR-ZXVF go1.2.linux-amd64.tar.gz

PS. There are also source package go1.2.src.tar.gz (as a code farm, do not look at the source code how to do, about the language in question can be directly read the codes: D)

2. Command-line Download

$HG Clone-u Release Https://code.google.com/p/go

Then run the Bash script installation

$CD go/src$. /all.bash

The installation succeeds when the word "all TESTS PASSED" appears after running All.bash.

(Of course Apt-get install Golang the simplest)

Assuming it was extracted into the $home/go,

Setting environment variables (refer to go Web programming) Here's just a brief description of the problem you've encountered.

System level

$CD/etc

$cat/etc/.profile

User Level

$cat $HOME/.profile mean as $cat ~/.profile

Bash Current process level

Enter export goroot= $HOME in terminal/go

or write your own *.sh file, and then run the script./*.sh,

Then look at the effect of the echo $GOROOT, no effect, why?

Don't worry, this is because the BASH environment variable is valid only in the current bash process, so you need to write this. ./*.sh

Add one in front. Indicates that the *.sh is executing in the current bash, otherwise the new bash goes to the export environment variable

To prevent the bash environment variables from being invalidated after a reboot, it is best to place them at the system level and user level.

Http://www.cnblogs.com/ghj1976/archive/2013/03/24/2979668.html This can be seen