Thanks a lot, Peter! 2017-03-26 11:07 GMT-07:00 peterGo <go.peter...@gmail.com>:
> Filip, > > ~ $ cd go/src > ~/go/src $ ./make.bash --no-clean > ##### Building Go bootstrap tool. > cmd/dist > > ##### Building Go toolchain using /home/peter/go1.4. > bootstrap/cmd/internal/dwarf > bootstrap/cmd/internal/src > bootstrap/cmd/internal/sys > bootstrap/cmd/asm/internal/flags > bootstrap/cmd/internal/bio > bootstrap/math/bits > bootstrap/cmd/compile/internal/syntax > bootstrap/cmd/internal/obj > bootstrap/math/big > bootstrap/cmd/internal/gcprog > bootstrap/debug/pe > bootstrap/cmd/internal/obj/arm > bootstrap/cmd/internal/obj/arm64 > bootstrap/cmd/internal/obj/mips > bootstrap/cmd/internal/obj/ppc64 > bootstrap/cmd/internal/obj/s390x > bootstrap/cmd/internal/obj/x86 > bootstrap/cmd/asm/internal/lex > bootstrap/cmd/link/internal/ld > bootstrap/cmd/asm/internal/arch > bootstrap/cmd/compile/internal/ssa > bootstrap/cmd/asm/internal/asm > bootstrap/cmd/asm > bootstrap/cmd/link/internal/amd64 > bootstrap/cmd/link/internal/arm > bootstrap/cmd/link/internal/arm64 > bootstrap/cmd/link/internal/mips > bootstrap/cmd/link/internal/mips64 > bootstrap/cmd/link/internal/ppc64 > bootstrap/cmd/link/internal/s390x > bootstrap/cmd/link/internal/x86 > bootstrap/cmd/link > bootstrap/cmd/compile/internal/gc > bootstrap/cmd/compile/internal/amd64 > bootstrap/cmd/compile/internal/arm > bootstrap/cmd/compile/internal/arm64 > bootstrap/cmd/compile/internal/mips > bootstrap/cmd/compile/internal/mips64 > bootstrap/cmd/compile/internal/ppc64 > bootstrap/cmd/compile/internal/s390x > bootstrap/cmd/compile/internal/x86 > bootstrap/cmd/compile > > ##### Building go_bootstrap for host, linux/amd64. > runtime/internal/sys > runtime/internal/atomic > runtime > encoding > errors > internal/race > internal/syscall/windows/sysdll > math > math/bits > sync/atomic > unicode > unicode/utf16 > unicode/utf8 > strconv > sync > reflect > io > syscall > internal/singleflight > sort > bytes > cmd/go/internal/web > encoding/base64 > encoding/binary > hash > internal/syscall/windows/registry > strings > internal/syscall/windows > container/heap > bufio > regexp/syntax > crypto > hash/adler32 > time > path > regexp > crypto/sha1 > internal/poll > os > os/signal > path/filepath > io/ioutil > fmt > context > flag > go/token > log > cmd/go/internal/str > encoding/json > go/scanner > net/url > text/template/parse > debug/dwarf > compress/flate > encoding/xml > os/exec > go/ast > text/template > debug/macho > compress/zlib > debug/elf > go/doc > go/parser > go/build > cmd/go/internal/cfg > cmd/go/internal/base > cmd/go/internal/buildid > cmd/go/internal/doc > cmd/go/internal/help > cmd/go/internal/load > cmd/go/internal/tool > cmd/go/internal/version > cmd/go/internal/work > cmd/go/internal/clean > cmd/go/internal/envcmd > cmd/go/internal/fix > cmd/go/internal/fmtcmd > cmd/go/internal/generate > cmd/go/internal/get > cmd/go/internal/list > cmd/go/internal/run > cmd/go/internal/test > cmd/go/internal/vet > cmd/go/internal/bug > cmd/go > > ##### Building packages and commands for linux/amd64. > cmd/asm > cmd/dist > cmd/compile > cmd/link > > --- > Installed Go for linux/amd64 in /home/peter/go > Installed commands in /home/peter/go/bin > ~/go/src $ > > Peter > > > On Sunday, March 26, 2017 at 1:22:02 PM UTC-4, Filip Gruszczyński wrote: >> >> Hi Ian, >> >> Thanks for responding! What I am looking for is to build only steps: >> >> ##### Building Go bootstrap tool. >> >> ##### Building Go toolchain using >> >> ##### Building go_bootstrap for host >> >> And then stop and be able to use the freshly produced go binary. No >> packages are going to be build, as I only need the runtime to test my >> changes. Where is the go binary produced at this point? >> >> On Monday, March 20, 2017 at 4:16:05 PM UTC-7, Ian Lance Taylor wrote: >>> >>> On Sun, Mar 19, 2017 at 3:29 PM, <grus...@gmail.com> wrote: >>> > >>> > I am tinkering with some runtime code and I would like to build only >>> the go >>> > binary to the test it on a small program I wrote. I don't see any >>> script in >>> > the source that would allow that, all of these also try to compile the >>> > standard library. I would like to avoid that, because it's easier for >>> me to >>> > test my changes first on smaller snippet of code. How can I build only >>> the >>> > main binary (and where it is going to be available)? >>> >>> I don't know if I understand you, but I think the answer to your >>> question is to avoid using the go tool. Instead of using `go build >>> x.go` use `go tool compile x.go && go tool link -o x x.o`. >>> >>> Ian >>> >> -- Filip Gruszczyński -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
