This is about as far as I got on the last attempt. Hopefully we can figure out how to generate code that will start to run on NonStop at some point soon. -Randall
On Thursday, May 6, 2021 at 10:35:27 p.m. UTC-4 Ian Lance Taylor wrote: > On Thu, May 6, 2021 at 6:16 AM Shiva <emailshiva...@gmail.com> wrote: > > > > Thank you, that helps. > > > > Now, as I continue to work on 'porting', I have a question. The go > compiler that will be used for creating this 'bootstrap' version of go1.16 > - does this come from the go1.16 windows binary or the go1.4 windows > binary? I ask because I have 'produced' both of them on different > directories (as I should) and wanted to make sure I set the right > 'GOROOT'/'GOPATH'/'GOBIN' variables and/or PATH to be able to produce the > bootstrap version. > > The Go compiler used to create the bootstrap compiler will be the Go > 1.16 Windows binary. > > Ian > > > > > On Wednesday, May 5, 2021 at 10:08:20 PM UTC+1 Ian Lance Taylor wrote: > >> > >> On Wed, May 5, 2021 at 1:00 PM Shiva <emailshiva...@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...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/d1337a2d-46ee-430c-bd92-bd7f3168b28en%40googlegroups.com > . > -- 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/58633e5c-ca77-4eec-88e7-4f559eb74dc5n%40googlegroups.com.
