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/vgo: vgo does not work on mac os x #31790

Closed
m00zi opened this issue May 1, 2019 · 2 comments

Comments

@m00zi
Copy link

commented May 1, 2019

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

$ go version
go version go1.12.4 darwin/amd64

go version go1.12.4 darwin/amd64 vgo:devel +b0a1c5df98

Does this issue reproduce with the latest release?

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

go env Output
$ go env

I have followed this URL to try the vgo:
https://research.swtch.com/vgo-tour

➜  hello vgo run hello.go
# command-line-arguments
runtime.strequal: relocation target runtime.memequal not defined for ABIInternal (but is defined for ABI0)
runtime.cgocall: relocation target runtime.asmcgocall not defined for ABIInternal (but is defined for ABI0)
runtime.cgoCheckWriteBarrier: relocation target runtime.systemstack not defined for ABIInternal (but is defined for ABI0)
runtime.cgoCheckTypedBlock: relocation target runtime.systemstack not defined for ABIInternal (but is defined for ABI0)
runtime.cgoCheckUsingType: relocation target runtime.morestackc not defined for ABI0 (but is defined for ABIInternal)
runtime.(*TypeAssertionError).Error: relocation target runtime.memequal not defined for ABIInternal (but is defined for ABI0)
runtime.panicwrap: relocation target internal/bytealg.IndexByteString not defined for ABIInternal (but is defined for ABI0)
runtime.memhash: relocation target runtime.aeshash not defined for ABIInternal (but is defined for ABI0)
runtime.(*itab).init: relocation target runtime.memequal not defined for ABIInternal (but is defined for ABI0)
runtime.lock: relocation target runtime.procyield not defined for ABIInternal (but is defined for ABI0)
runtime.notesleep: relocation target runtime.asmcgocall not defined for ABIInternal (but is defined for ABI0)
runtime.notetsleep_internal: relocation target runtime.asmcgocall not defined for ABIInternal (but is defined for ABI0)
runtime.(*mheap).sysAlloc: relocation target runtime.memmove not defined for ABIInternal (but is defined for ABI0)
runtime.mallocgc: relocation target runtime.publicationBarrier not defined for ABIInternal (but is defined for ABI0)
runtime.mallocgc: relocation target runtime.memclrNoHeapPointers not defined for ABIInternal (but is defined for ABI0)
runtime.mallocgc: relocation target runtime.systemstack not defined for ABIInternal (but is defined for ABI0)
runtime.persistentalloc: relocation target runtime.systemstack not defined for ABIInternal (but is defined for ABI0)
runtime.persistentalloc1: relocation target runtime.morestackc not defined for ABI0 (but is defined for ABIInternal)
runtime.typedmemmove: relocation target runtime.memmove not defined for ABIInternal (but is defined for ABI0)
runtime.typedslicecopy: relocation target runtime.memmove not defined for ABIInternal (but is defined for ABI0)
runtime.memclrHasPointers: relocation target runtime.memclrNoHeapPointers not defined for ABIInternal (but is defined for ABI0)
/usr/local/go/pkg/tool/darwin_amd64/link: too many errors
@thepudds

This comment has been minimized.

Copy link

commented May 1, 2019

vgo has been merged into the main Go repository, and its functionality was included with Go 1.11 as the new "versioned Go modules" feature.

At this point, rather than using vgo, a much better option is to just use Go 1.12 with modules enabled. The functionality can be enabled via the opt in GO111MODULE environment variable. You can for example set GO111MODULE=on, or see here for a slightly longer description of how to opt in to modules with Go 1.11 or 1.12.

Also, rather than trying to follow the old vgo-tour you were following, a better introduction is now https://blog.golang.org/using-go-modules (which happens to be partially adapted from that older vgo-based introduction).

See also #27563, including #27563 (comment), which states:

Once Go 1.12 is out, Go 1.10 will be deprecated, at which point all supported versions of Go will have module support. Then we can remove vgo entirely (maybe a month or so after the Go 1.12 release).

@thepudds thepudds changed the title vgo does not work on mac os x x/vgo: vgo does not work on mac os x May 1, 2019

@gopherbot gopherbot added this to the vgo milestone May 1, 2019

@bradfitz

This comment has been minimized.

Copy link
Member

commented May 1, 2019

Yeah, vgo is no longer supported. It served its purpose, but at this point just use go.

@bradfitz bradfitz closed this May 1, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.