Windows 10 build failed: running gcc failed: exit status 1 #78
Comments
|
Hi @flerka From looking around, it looks like most of the time it's trying to link against the 32bits library, would you have a way to check that ? The basic example from cgo works because it doesn't link any external code, just compile everything in the same file |
|
Hi @Viq111.
You were totally right about that. Before installing 64 version of go, 32 version was installed accidently. And even after it (32bit go) was uninstalled and 64bit go installed - some folders were not deleted from 32bit env. Some packages etc. So after reading your message I uninstalled go and manually removed all go-related files from all |
What version of Go are you using (
go version)?go version go1.13.6 windows/amd64
What operating system and processor architecture are you using (
go env)?Windows 10
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\homepc\AppData\Local\go-build
set GOENV=C:\Users\homepc\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\homepc\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=c:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\homepc\AppData\Local\Temp\go-build692364802=/tmp/go-build -gno-record-gcc-switches
What did you do?
Build in windows 10 failed
What did you expect to see?
Should build successfully
What did you see instead?
I initially got gcc not found error, so I installed TDM-GCC-64 and add path C:\TDM-GCC-64\bin, then, I got above error
I think it's related to this issue #63
Basic example from cgo (https://golang.org/cmd/cgo/, where
C code may call function pointers received ...) compiles and runs successfully, so I don't think there are some problems with my local installation.The text was updated successfully, but these errors were encountered: