On Wed, May 5, 2021 at 1:00 PM Shiva <emailshivasubraman...@gmail.com> wrote: > > So I've now done the following steps as you suggested after removing all the > previous traces of Go from my machine to start from the scratch. > > 1. Install go1.4 > 2. Set GOROOT_BOOTSTRAP to go1.4 > 3. git clone go1.16 > 4. Run make.bat to 'make' Go on windows just to confirm that it does build > fine (which it clearly does) > > Now, I suppose I have to 'port' the current go1.16 src folder by creating > 'nsx' files similar to 'linux'? I'm now working on them and hopefully will be > able to break some ground.
Yes. > But I also have a question - I think the reason we chose to port go 1.4 > instead of the latest source is because the latest source requires a > pre-existing go compiler and Nonstop (our target) machine didn't have one. I > suppose your earlier response suggests that as long as the intermediate > system has a pre-existing go compiler that can be used, it doesn't matter if > the target environment doesn't have a Go compiler - we can still bootstrap > the latest version of the source. I just wanted to confirm this as I > continued. Yes. That is what bootstrap.bash is for. See the description in the comment near the start of bootstrap.bash. Ian -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcXqoxMMi9eWczvvHmSMK4Pq6dj5q%2B5gK1h%3D8b2iAaogiA%40mail.gmail.com.
