Home → Problems →

Go 1.4 support

• Edit

Keiji Yoshida

14 Dec, 2014 03:10 PM

I noticed that the version of Go on AppVeyor is still 1.3. Are there any ways to use Go 1.4 on AppVeyor now?

1. Support Staff 1 Posted by Feodor Fitsner on 14 Dec, 2014 04:47 PM

   

   You may just download Go 1.4 zip package during the build and extract it to C:\Go folder. Add these commands to your install phase:

   install:
     - rd C:\Go /s /q
     - appveyor DownloadFile https://storage.googleapis.com/golang/go1.4.windows-386.zip
     - 7z x go1.4.windows-386.zip -oC:\ >nul
   

   • Edit

2. 2 Posted by Keiji Yoshida on 15 Dec, 2014 12:26 AM

   

   Thanks! I'll try it!

   • Edit

3. 3 Posted by Joel Scoble on 19 Feb, 2015 06:09 PM

   

   It would be helpful if AppVeyor could support 1.4 as it has fixes that affect Windows. This would save on AppVeyor bandwidth and resources that downloading and extracting 1.4 for testing would use.

   • Edit

4. Support Staff 4 Posted by Feodor Fitsner on 19 Feb, 2015 06:34 PM

   

   Sure, will deploy it this week.

   • Edit

5. 5 Posted by Joel Scoble on 19 Feb, 2015 07:58 PM

   

   Feodor Fitsner: that is great news.

   Thank you.

   • Edit

6. Support Staff 6 Posted by Feodor Fitsner on 20 Feb, 2015 05:10 AM

   

   It's been deployed.

   • Go 1.4.2 x86 (C:\go - default in PATH)
   • Go 1.4.2 x64 (C:\go-x64)
   • Edit

7. 7 Posted by rjeczalik on 21 Feb, 2015 08:19 PM

   

   Thanks for bumping Go version on your builders.

   One suggestion though - shouldn't the amd64 be the default one? Changing default Go target architecture from amd64 to 386 is going to break people's builds, those which use testing with -race as Go does not support -race on 386. Alternatively some notification to those affected, to put GOROOT: c:\go-x64 in theirs appveyor.yml configuration files.

   • Edit

8. Support Staff 8 Posted by Feodor Fitsner on 21 Feb, 2015 08:37 PM

   

   Yeah, that's good to know, thanks.

   -Feodor

   • Edit

9. 9 Posted by Owen Waller on 26 Feb, 2015 08:34 PM

   

   Hi,

   And following up on rjeczalik's comment. The 64bit version should be a default on a 64bit OS.

   But, rather than set the environmental variables in the appveyor.yml, if I set them on a per project basis in the Settings/Environment screen as:

   GOROOT : C:\go-x64
   PATH : %GOROOT%\bin;%PATH%

   Then I should be using the 64bit/amd64 version of go.
   But as you can see from the build results - see the URL at the end - a call to go version tells me that it's windows/386 i.e. the 32 bit version.

   So I am still picking up the i386 version of go, not the amd64 version - which I need for go's race detector.

   Also as you can see from the build results the 64bit version of go's bin directory is the fist element in the PATH and so should override the 32bit version of go in c:\go\bin which is the last but 2 element in the PATH.

   Also if I set the environmental variables in the CMD scripts used to create the build, I get the same results.

   So something is up, but this is not behaving as I would expect.

   • Edit

10. Support Staff 10 Posted by Feodor Fitsner on 26 Feb, 2015 08:45 PM

    

    Hi Owen,

    You should defined them as:

    GOROOT : C:\go-x64
    PATH : C:\go-x64\bin;%PATH%
    

    However, I agree that it makes sense having x64 by default. We are going to change that with today's deployment:

    • C:\go will contain x64
    • C:\go-x86 will contain x86
    • C:\go-x64 will be symbolink link to C:\go

    Hope that helps.

    • Edit

11. Support Staff 11 Posted by Feodor Fitsner on 27 Feb, 2015 05:17 AM

    

    OK, guys, it's been swapped. C:\go contains x64 now.

    • Edit

12. 12 Posted by rjeczalik on 27 Feb, 2015 09:47 AM

    

    Just a heads up. The symlinked `c:\go-x64` does not work.

    go: cannot find GOROOT directory: c:\go-x64
    Command exited with code 2

    https://ci.appveyor.com/project/rjeczalik/notify-246/build/271

    • Edit

13. Support Staff 13 Posted by Feodor Fitsner on 27 Feb, 2015 02:26 PM

    

    Yeah, seems like Go doesn't notice symlinks. Will just remove it next time.

    -Feodor

    • Edit

14. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:54 AM.