[go-nuts] Re: Building Go 1.21 for openbsd/386

2023-02-28 Thread 'drc...@google.com' via golang-nuts
Try also GOMAXPROCS=1 ? At some point not too long ago we made that dial down the concurrency in the compiler (before, it would do concurrent builds/compiles anyway) and that should reduce the maximum footprint. On Wednesday, February 22, 2023 at 1:42:56 PM UTC-5 Jan Mercl wrote: > The subject

[go-nuts] Re: Building Go

2018-03-08 Thread matthewjuran
While an old Go program will compile with new versions, new Go programs may not compile with old versions due to added standard library APIs. Matt On Thursday, March 8, 2018 at 10:32:35 AM UTC-6, Krzysztof Kwiatkowski wrote: > > Hi, > > > I've quite newbe question, but I would like to double-ch

Re: [go-nuts] Re: Building Go from Source / Managing my ${GOROOT}

2017-02-23 Thread Steve Mynott
Peter, That will no longer work in go 1.8 since GOPATH is set to $HOME/go by default and what you describe will also set GOROOT to the same directory and the two environment variables have to point at different directories. ("go env" is useful for debugging this) One solution is "git clone https

[go-nuts] Re: Building Go from Source / Managing my ${GOROOT}

2017-02-19 Thread peterGo
Ayan, It's not idiomatic because you are setting and using GOROOT. Leave that to the compiler. For example, with no GOROOT, $ cd $HOME $ git clone https://go.googlesource.com/go $ cd go/src $ ./make.bash Peter On Saturday, February 18, 2017 at 5:51:09 PM UTC-5, Ayan George wrote: > > I'm some

[go-nuts] Re: Building Go 1.7.3 from source on windows

2016-10-31 Thread Henry
Hi Dave, Thanks for pointing towards the right direction. I did some major cleanups on my machine and sorted out the environment variables. The build went smoothly afterwards with all tests passed. I guess it was time to clean up the machine anyway. Thanks again. :) Henry On Monday, October

[go-nuts] Re: Building Go 1.7.3 from source on windows

2016-10-30 Thread Dave Cheney
> MYSQL not recognized as internal/external command ^ all.bat should never output that. I think you have something that pretends to be cmd.exe, or possibly something that pretends to be gcc.exe in your path. > Is there any way to verify my build is complete and it works correctly? If you don'