> I had installed go following > http://docs.9front.org/building-go
Those instructions don't actually install go into /sys/lib/go/amd64-1.15.2 They install go into /tmp/go, which is then bound dynamically onto /sys/lib/go/amd64-1.15.2 This has two consequences: - every time you run go, you must first ensure that /tmp/go is bound onto $GOROOT in the current process environment - your /tmp had better not be too temporary (some people use ramfs to mount /tmp as an in-memory filesystem) I think it would be safer to install go into the actual /sys/lib tree, or (eg if you're on a shared system without write permission in /sys/lib), into your home directory and add the relevant bind command to your $home/lib/profile > And other than the go binary I do not see any go files under src. The .go files are in subdirectories. 'du -a $GOROOT/src' should show at least 4000 of them. > Would I even have a cache considering i've never successfully built a go > project yet? Installing go by building from source will cache lots of stuff in $home/lib/cache/go-build. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T80ee3327f2f3dc57-Mc5b4006f4c7a1d740a3a8a8b Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
