Closed alexbrainman closed 3 years ago
CC @jordanrh1
@jordanrh1, where are the windows-arm builders?
Per our https://github.com/golang/go/wiki/PortingPolicy, we're likely to remove ports that don't have builders for long periods of time.
@jstarks can you help with this issue? It would be sad, if windows-arm code gets removed just because we don't have the builder.
Thank you.
Alex
There's also https://github.com/WOA-Project/WOA-Deployer-Rpi these days.
I am able to successfully build 1.14.4 using the instructions Alex posted in his first message, except adding GOARM=7 to the bootstrap.bash environment. This is on Windows 10 ARM64 with a checkout of 1.14.4:
Therefore, I believe this issue can be closed as fixed.
However, this problem -- https://github.com/golang/go/issues/39465 -- now exists with gitmaster/1.15.
I am able to successfully build 1.14.4 using the instructions Alex posted in his first message, except adding GOARM=7 to the bootstrap.bash environment.
Great. Can you try and run all.bat, and see if it pass too.
Also, please, workout how to run windows-arm builder in your environment.
@bcmills do you know how to run windows-arm builder? If not, do you know who knows?
Thank you.
Alex
@bcmills do you know how to run windows-arm builder? If not, do you know who knows?
https://github.com/golang/go/issues/36439#issuecomment-641706004
@bcmills do you know how to run windows-arm builder? If not, do you know who knows?
Sounds good. Lets see what happens.
Alex
Alex posted in his first message, except adding GOARM=7 to the bootstrap.bash environment.
Maybe I made mistake, and not specified GOARM=7 to bootstrap.bash. But I think it was more likely that you have more memory in your OS. If you look at the error above
Building Go toolchain2 using go_bootstrap and Go toolchain1.
# cmd/compile/internal/ssa
runtime: VirtualAlloc of 4194304 bytes failed with errno=1455
fatal error: out of memory
I think Raspberry PI just does not have enough memory for make.bat to run. Perhaps it needs a swap file or something.
Alex
Great. Can you try and run all.bat, and see if it pass too.
I wonder if shelling out to netsh.exe is a WOW64 issue, since I'm running arm32 on an arm64 system.
Anyway, there's at least one failure in there.
This is 1.14.4, by the way. As mentioned above, 1.15 has a crashing compiler due to https://github.com/golang/go/issues/39465
pprof fails extremely elaborately.
This is 1.14.4, by the way.
I did not expect all.bat to pass for 1.14. It used to work for go1.12 or thereabout. But all that can be fixed once we get the builder running.
Alex
This is an old issue and the windows/arm builder is now up and... crashing. But with a different error. So I'd say: let's close here and keep #39465 and/or #42786 to track the current crash.
It has been awhile since I have seen windows-arm PASS or FAIL on https://build.golang.org, and I decided to see if Go tip still builds on windows arm.
I managed to install Windows IoT on my Raspberry Pi 3.
Then I build bootstrap version of Go for windows arm by running
against go1.12.4 Git tag on my Linux computer. And I copied created directory onto my Windows RPI using Windows file share.
I could not find Git program that would run on Windows IoT, so I used my Windows 10 computer to clone Go repo onto file share on Windows IoT. I checked out go1.12.4 Git tag.
I used this command file to setup my Windows IoT environment
and then I run
make
command.I expected
make
command to complete successfully, but it fails withI also tried 84066f1 instead of go1.12.4 for bootstrapping. I also tried running
make
against 84066f1 instead of go1.12.4. I also tried to addGOARM=7
environment variable to both bootstrap build andmake
command. All to no good - I get the same result.I also cannot just increase RPI memory. So I looked for a way to get my RPI page file bigger or something. But I could not find any information on the web.
Looking for suggestions of how I can advance my
make
command progress further.Alex