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.

Sign up for GitHub

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

Jump to bottom

x/mobile/gl: go get fails on windows_386 #15763

Closed

tpng opened this issue May 20, 2016 · 1 comment

Labels

Milestone

tpng commented May 20, 2016

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?
go version go1.6.2 windows/386
What operating system and processor architecture are you using (go env)?
Windows 7 64-bit
What did you do?
go get -u golang.org/x/mobile/gl
What did you expect to see?
No error messages.
What did you see instead?

# golang.org/x/mobile/gl
..\..\..\golang.org\x\mobile\gl\work_windows.go:104: missing function body for "fixFloat"

The text was updated successfully, but these errors were encountered:

quentinmit added this to the Unreleased milestone

gopherbot commented Oct 26, 2016

CL https://golang.org/cl/32113 mentions this issue.

gopherbot closed this as completed in


      golang/mobile@d362015

golang locked and limited conversation to collaborators

gopherbot added the FrozenDueToAge label

imWildCat pushed a commit to imWildCat/go-mobile that referenced this issue


          x/mobile/gl: fix building on windows/386

658587f

Fixes golang/go#15763

Change-Id: Iead7d69367ee5c821aefd1faed56bb3b259b6a62
Reviewed-on: https://go-review.googlesource.com/32113
Reviewed-by: David Crawshaw <crawshaw@golang.org>

imWildCat pushed a commit to imWildCat/go-mobile that referenced this issue


          x/mobile/gl: fix building on windows/386

1186dd5

Fixes golang/go#15763

Change-Id: Iead7d69367ee5c821aefd1faed56bb3b259b6a62
Reviewed-on: https://go-review.googlesource.com/32113
Reviewed-by: David Crawshaw <crawshaw@golang.org>

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.