any Windows 8 Go users?

[minux]

As discussed recently, Dave Cheney is preparing a CL regarding the minimum system

requirement for Go. (The relevant discussion is here: https://codereview.appspot.com/7225047/)

As none of the people who participate so far in that discussion uses Windows 8, we

can't be sure whether we can label windows 8 as a support platform of Go or not.

So if anyone uses Go on windows 8, could you please report your experiences?

Are there anyone who has successfully compiled and tested Go tip from source on that

platform (both 386 and amd64)?

Thank you.

Cheers.

[Nate Finch]

I just brought up a win8 vm for compatibility testing at work,  I can download the source and try running it either tomorrow morning or Monday.  Anything you want tested besides running the tests?

--
 
 

[Dave Cheney]

./all.bat should be sufficient, but if you have code from your projects, it wouldn't hurt to try building and running that.

[Nate Finch]

I think I replied directly to Dave by accident, since I'm not seeing the response here.

I'll run the tests and build/test/run a couple of my own projects, and report back.  Glad to be able to help :)

[Job van der Zwan]

I always dual-boot to Linux, but my laptop has Windows 8 installed as well (because touchscreen + studying interaction design). I'll give it a try (amd64).

[Job van der Zwan]

[Arie van Wingerden]

Where can I find the "Go tip" sources?

Thx, Arie

2013/1/27 Job van der Zwan <j.l.van...@gmail.com>

--
 
 

[Job van der Zwan]

On Sunday, 27 January 2013 14:34:54 UTC+1, Arie van Wingerden wrote:

Where can I find the "Go tip" sources?

Thx, Arie

http://golang.org/doc/install/source

Remove "-u release" from the hg clone step.

[Arie van Wingerden]

Hi,

I just built Go in W8 from source and got some errors from the tests.

See attached logfile.

/Arie

2013/1/27 Job van der Zwan <j.l.van...@gmail.com>

On Sunday, 27 January 2013 14:34:54 UTC+1, Arie van Wingerden wrote:

--
 
 

[Arie van Wingerden]

Ah, I missed the "Remove the -u release" will try now again ... ;-)

2013/1/27 Arie van Wingerden <xap...@gmail.com>

[Arie van Wingerden]

Now I used the appropriate hg command.

Still some tests do not pass.

See attached logfile.

/Arie

2013/1/27 Arie van Wingerden <xap...@gmail.com>

[Patrick Mylund Nielsen]

I would suggest adding the Windows Server builds, e.g. Windows Server 2012 (Windows 8.)

I can test further (including with tip) when I get home, but I'm running several Go production applications on Windows 8 and Windows Server 2012, using Go 1.0.3. The apps primarily do crypto, net/http and encoding/*. So far I've had a few errors with WSARecv tcp (host is no longer available, even though it is, and "The semaphore timeout period has expired" whilst performing http requests.) I've yet to determine if these winsock errors are actually Go-on-8 issues, or stem from running Windows on Amazon...

Everything else has worked great so far.

--
 
 

[brainman]

Thank you for testing. I knew that TestDialTimeoutHandleLeak is a bit flaky - I will try to rewrite it.

Alex

[brainman]

Thank you form the report. Feel free to report problems, perhaps there is something we can do.

Alex

[brainman]

Lots of errors. I need time to investigate. What is your OS called? What kind of computer are you running? Thank you.

Alex

[Maxim Khitrov]

On Sat, Jan 26, 2013 at 5:02 PM, minux <minu...@gmail.com> wrote:

> So if anyone uses Go on windows 8, could you please report your experiences?
>
> Are there anyone who has successfully compiled and tested Go tip from source
> on that
> platform (both 386 and amd64)?

Windows 8 all.bat outputs for 386 and amd64 are attached (tip version
aee6d7fe395a). Did I need to do anything other than "set GOARCH=386"
to build the 32-bit version? That one seems to have failed, but I
don't know what "_image_base__(0): not defined" means.

- Max

[brainman]

On Monday, 28 January 2013 11:54:20 UTC+11, Maxim Khitrov wrote:

Windows 8 all.bat outputs for 386 and amd64 are attached (tip version
aee6d7fe395a).

Looks good to me. Thank you very much.

 

Did I need to do anything other than "set GOARCH=386"

to build the 32-bit version? ...

Not as far as I know. That is what I would do too.

 

That one seems to have failed, but I
don't know what "_image_base__(0): not defined" means.

This part tests cgo. Go tools will easily compile for whatever cpu / os you like. But for cgo you have to employ gcc. I suspect your gcc can compile for amd64 only. But I do not know much about that. Perhaps others will help. 

Alex

[Arie van Wingerden]

I have Windows 8 pro 332 bit on a AMD Athlon X2 245 processor (x64) with 4GB RAM.

/Arie

2013/1/27 brainman <alex.b...@gmail.com>

Lots of errors. I need time to investigate. What is your OS called? What kind of computer are you running? Thank you.

Alex

--

[Nate Finch]

Attached is my build and test output, no errors that I see, though I do see this at the end:

# ..\misc\cgo\life

go run: no go files listed

Not sure if that denotes a problem or not.

Environment:

Stock Windows 8 Enterprise 32 bit (VM in VMWare player with Win7 64 bit host OS)

Dell Laptop w/ Core i7 64 bit CPU, SSD, w/ 4GB RAM for VM

Also, tested my own code, which works just fine.

[Daniel Theophanes]

I tested this last fall when it came out. Yeah, it works just fine on both Windows 8 and Windows Server 2012, cgo and all. There's very little change between Windows 7 and Windows 8 APIs.

[minux]

Thank you all for the info!

Although there might be some little bugs in the tests, Windows 8 is a supported platform

of Go.

[Nate Finch]

That's awesome :)

[Daniel Theophanes]

Make sure you call out that Windows 8 RT (arm) is unsupported.

[Tech163]

Builds fine on Windows 2012 on azure VM.

Tech163

> --
>
>

[brainman]

On Monday, 28 January 2013 18:20:26 UTC+11, Arie van Wingerden wrote:

I have Windows 8 pro 332 bit on a AMD Athlon X2 245 processor (x64) with 4GB RAM.

/Arie

Thank you. I have created an issue http://code.google.com/p/go/issues/detail?id=4723. I will try to investigate it further when I have time.

Alex

[brainman]

Arie,

I have posted couple of questions here http://code.google.com/p/go/issues/detail?id=4723#c3. Please, comment there, if you are still interested. Thank you.

Alex

[Jay Weisskopf]

Nevermind, I was mistaken. The MSI added Go to the PATH, but my command prompts didn't reflect that until I restarted. Sorry.

- Jay