[go-nuts] Wrestling with Mingw64 on Windows

2017-01-30 Thread Jacob Martin
I'd advice you to use bash on Ubuntu on windows to compile cgo programs on windows. It's easy to use and works. -- 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 g

Re: [go-nuts] Wrestling with Mingw64 on Windows

2017-01-30 Thread Michael Banzon
The name of the MINGW suggest that it is 32-bit - are you sure you are running a full 64-bit tool chain? What does the --version of the gcc output? On Mon, Jan 30, 2017, 17:30 Arie van Wingerden wrote: > > 2017-01-30 12:04 GMT+01:00 Arie van Wingerden : > > set PATH=%GOROOT%\%MINGWPATH%\bin;%P

Re: [go-nuts] Wrestling with Mingw64 on Windows

2017-01-30 Thread Arie van Wingerden
2017-01-30 12:04 GMT+01:00 Arie van Wingerden : > set PATH=%GOROOT%\%MINGWPATH%\bin;%PATH% > typo: ​should be: set PATH=%GOROOT%\bin;%MINGWPATH%;%PATH%​ behavior further as described -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubs

[go-nuts] Wrestling with Mingw64 on Windows

2017-01-30 Thread Arie van Wingerden
I try to use CGO on Windows I installed Mingw64 from here: https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Automated%20Builds/ My Go env vars are like so: set CC=i686-w64-mingw32-gcc.exe set GOROOT=e:\programs\go64 set GOPATH=e:\src\go set GOOS=wi