shithub: docs.9front.org

Download patch

ref: ba1d7b8b5be56a039dc2eb9776f90ad70636467b
parent: 23520cdd0314a2ea171ce8a7c1047fbd805a7e83
author: Moody <j4kem00dy@gmail.com>
date: Thu Nov 19 12:46:48 EST 2020

Added some missing ':' in building-go

--- a/building-go.md
+++ b/building-go.md
@@ -2,7 +2,7 @@
 ===
 
 First we'll need a suitable location for our 'GOROOT', the standard convention is
-to place it in '/sys/lib/go/$objtype-$version'.
+to place it in '/sys/lib/go/$objtype-$version':
 
 	mkdir -p /sys/lib/go
 	cd /sys/lib/go
@@ -19,7 +19,7 @@
 bootstrap and desired build version. It is best to use to the latest bootstrap when possible and
 some intermediate builds may be required depending on the age of the bootstrap.
 
-Next we'll need to configure both 'GOROOT' and 'GOROOT_BOOTSTRAP'
+Next we'll need to configure both 'GOROOT' and 'GOROOT_BOOTSTRAP':
 
 	GOROOT_BOOTSTRAP=/sys/lib/go/go-plan9-amd64-bootstrap
 	GOROOT=/sys/lib/go/amd64-1.15.2
@@ -34,8 +34,8 @@
 
 	bind -b $GOROOT/bin /bin
 
-If you have the memory available on your system it may be faster to build using a ramfs in '/tmp'.
-Setting 'GOROOT_FINAL' to the desired final location of 'GOROOT' will help in building.
+Optionally, if you have the memory available on your system,
+it may be faster to build using a ramfs in '/tmp':
 
 	mkdir -p /sys/lib/go/
 	ramfs
@@ -49,7 +49,7 @@
 	make.rc
 	dircp /tmp/amd64-1.15.2 /sys/lib/go/
 
-You can verify that GOROOT has been set properly using:
+You can verify that 'GOROOT' has been set properly using:
 
 	$GOROOT_FINAL/bin/go env