Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/tools/cmd/splitdwarf: build failure on Windows due to unskipped files #32212

Closed
nellierosenfield opened this issue May 23, 2019 · 2 comments
Closed
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@nellierosenfield
Copy link

What version of Go are you using (go version)?

$ go version 
go1.12.5 windows/am64

Does this issue reproduce with the latest release?

Yes, I have the latest Go on my system.

What operating system and processor architecture are you using (go env)?

go env Output
$ go env
set GOARCH=amd64
set GOBIN=
set GOCACHE=~\AppData\Local\go-build
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=~\Desktop\Development\gocode
set GOPROXY=
set GORACE=
set GOROOT=C:\Go
set GOTMPDIR=
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
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=~\AppData\Local\Temp\go-build501080342=/tmp/go-build -gno-record-gcc-switches

What did you do?

While attempting to retrieve tools (mainly godoc) by using go get golang.org/x/tools/cmd/... in my shell via Emacs, an error seems to be thrown by golang.org/x/tools/cmd/splitdwarf.

What did you expect to see?

Nothing, as an indication that all went well.

What did you see instead?

This is what I get in my shell:

# golang.org/x/tools/cmd/splitdwarf
runtime.main_main·f: function main is undeclared in the main package

However, if I try to retrieve godoc directly via go get golang.org/x/tools/cmd/godoc, I do not receive this message.

Sidenote

This doesn't affect me as I am not using splitdwarf (at least to my knowledge). I don't know how to solve this nor what caused this error, as I am pretty new to Go. Therefore, I wanted to bring it to the attention of highly capable individuals : ). Maybe it will benefit someone out there.

Thank you very much for your time and attention,
Nilaja D Williams

@josharian
Copy link
Contributor

cc @dr2chase

@gopherbot
Copy link

Change https://golang.org/cl/178699 mentions this issue: cmd/splitdwarf: fix skip on Windows

@bradfitz bradfitz added the NeedsFix The path to resolution is known, but the work has not been done. label May 23, 2019
@bradfitz bradfitz added this to the Go1.13 milestone May 23, 2019
@bradfitz bradfitz changed the title splitdwarf runtime issue: "function main is undeclared in the main package" x/tools/cmd/splitdwarf: build failure on Windows due to unskipped files May 23, 2019
@golang golang locked and limited conversation to collaborators May 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

No branches or pull requests

4 participants