go/src/run.rc

#!/bin/rc -e
# Copyright 2012 The Go Authors. All rights reserved.
# Use of this source code is governed by a BSD-style
# license that can be found in the LICENSE file.

rfork e

if(! test -f ../bin/go){
	echo 'run.rc must be run from $GOROOT/src after installing cmd/go' >[1=2]
	exit wrongdir
}

eval `{../bin/go env}

GOPATH = () # we disallow local import for non-local packages, if $GOROOT happens
            # to be under $GOPATH, then some tests below will fail
GOBIN = () # Issue 14340
GOFLAGS = ()
GO111MODULE = ()

exec ../bin/go tool dist test -rebuild $*
build: dist-based build for Plan 9 R=rsc, iant, iant, seed CC=golang-dev https://golang.org/cl/5608059 2012-05-01 23:32:46 -06:00			`#!/bin/rc -e`
			`# Copyright 2012 The Go Authors. All rights reserved.`
			`# Use of this source code is governed by a BSD-style`
			`# license that can be found in the LICENSE file.`

build: do not set GOBIN on Plan 9 Also, I synced the rc files with changes that have been made to make.bash, etc. R=seed, rminnich, r CC=golang-dev https://golang.org/cl/7389049 2013-02-26 10:25:46 -07:00			`rfork e`

run.{bash,bat,rc}: use ../bin/go instead of the go binary in $PATH https://golang.org/doc/contribute.html#quick_test currently suggests running 'make.bash' and 'run.bash' separately, but 'run.bash' potentially uses a 'go' command resolved from the wrong GOROOT, which in turn sets the wrong GOROOT for further commands. Updates #32674 Updates #17896 Change-Id: I4925d478d0fc7351c4f6d40830ab17d4d688348d Reviewed-on: https://go-review.googlesource.com/c/go/+/223741 Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Katie Hockman <katie@golang.org> 2020-03-17 08:22:39 -06:00			`if(! test -f ../bin/go){`
			`echo 'run.rc must be run from $GOROOT/src after installing cmd/go' >[1=2]`
			`exit wrongdir`
			`}`

			eval `{../bin/go env}
build: do not set GOBIN on Plan 9 Also, I synced the rc files with changes that have been made to make.bash, etc. R=seed, rminnich, r CC=golang-dev https://golang.org/cl/7389049 2013-02-26 10:25:46 -07:00
build: fix typos in run.rc LGTM=bradfitz R=jas, bradfitz CC=golang-codereviews https://golang.org/cl/52940044 2014-01-27 22:17:38 -07:00			`GOPATH = () # we disallow local import for non-local packages, if $GOROOT happens`
build: do not set GOBIN on Plan 9 Also, I synced the rc files with changes that have been made to make.bash, etc. R=seed, rminnich, r CC=golang-dev https://golang.org/cl/7389049 2013-02-26 10:25:46 -07:00			`# to be under $GOPATH, then some tests below will fail`
build: unset GOBIN during build Fixes #14340 Change-Id: I43e1624fafc972fb868708c3857fc8acf1bfbbd7 Reviewed-on: https://go-review.googlesource.com/23255 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> Reviewed-by: Rob Pike <r@golang.org> 2016-05-19 11:43:04 -06:00			`GOBIN = () # Issue 14340`
cmd/go: add $GOFLAGS environment variable People sometimes want to turn on a particular go command flag by default. In Go 1.11 we have at least two different cases where users may need this. 1. Linking can be noticeably slower on underpowered systems due to DWARF, and users may want to set -ldflags=-w by default. 2. For modules, some users or CI systems will want vendoring always, so they want -getmode=vendor (soon to be -mod=vendor) by default. This CL generalizes the problem to “set default flags for the go command.” $GOFLAGS can be a space-separated list of flag settings, but each space-separated entry in the list must be a standalone flag. That is, you must do 'GOFLAGS=-ldflags=-w' not 'GOFLAGS=-ldflags -w'. The latter would mean to pass -w to go commands that understand it (if any do; if not, it's an error to mention it). For #26074. For #26318. Fixes #26585. Change-Id: I428f79c1fbfb9e41e54d199c68746405aed2319c Reviewed-on: https://go-review.googlesource.com/126656 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Rob Pike <r@golang.org> 2018-07-28 23:10:02 -06:00			`GOFLAGS = ()`
build: clear GO111MODULE during make.bash etc The standard build assumes the variable is unset. Make it so, like we do for GOFLAGS, GOBIN, and so on. Change-Id: I4ad5695f8021b08bd1a35dd99112970a813d247c Reviewed-on: https://go-review.googlesource.com/c/149959 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> 2018-11-16 10:47:33 -07:00			`GO111MODULE = ()`
build: dist-based build for Plan 9 R=rsc, iant, iant, seed CC=golang-dev https://golang.org/cl/5608059 2012-05-01 23:32:46 -06:00
run.{bash,bat,rc}: use ../bin/go instead of the go binary in $PATH https://golang.org/doc/contribute.html#quick_test currently suggests running 'make.bash' and 'run.bash' separately, but 'run.bash' potentially uses a 'go' command resolved from the wrong GOROOT, which in turn sets the wrong GOROOT for further commands. Updates #32674 Updates #17896 Change-Id: I4925d478d0fc7351c4f6d40830ab17d4d688348d Reviewed-on: https://go-review.googlesource.com/c/go/+/223741 Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Katie Hockman <katie@golang.org> 2020-03-17 08:22:39 -06:00			`exec ../bin/go tool dist test -rebuild $*`