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/sys/unix: relocation target golang.org/x/sys/unix.Syscall6 not defined for ABIInternal (but is defined for ABI0) #30427
Comments
I have the same issue though I use just |
You need to update to a newer version of golang.org/x/sys/unix. |
From Vgo is a prototype of what the go command might look like with integrated support for package versioning. Download and install with:
Then run "vgo" instead of "go". |
Already did.
|
In the current golang.org/x/sys/unix sources, |
@mmhyamin What is the git revision of your golang.org/x/sys/unix sources? |
|
I am facing the same issue as well. There is some info on 1.12 compatibility
And bazelbuild/rules_go#1893 but so far I can't any useful info on how to fix it.
Edit:
|
@alekc It sounds like you are building with Bazel? Bazel may need to be updated to support the new ABI support. I don't know what the status of |
Nope I am building with vgo, Bazel is not involved. Weird thing is that I
am able to compile it without any issue on windows with
```
go version go1.12 windows/amd64 vgo:devel +b0a1c5df98
```
but if fails during compilation on linux (Debian Jessie).
There might be some dll issue, but so far I couldn't find what it is. Since
the project is in development phase for now, I've switched to Go 1.11 for
linux compilation.
…On Wed, 13 Mar 2019 at 02:34, Ian Lance Taylor ***@***.***> wrote:
@alekc <https://github.com/alekc> It sounds like you are building with
Bazel? Bazel may need to be updated to support the new ABI support.
I don't know what the status of vgo is.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#30427 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AASe15Up55DdAdWOvj59J5QbGAqZPengks5vWGO_gaJpZM4bTy62>
.
|
Has vgo been kept up to date with Go 1.12? Why not use the normal go tool? I think that at this point everything in vgo has been moved to the the go tool. |
I am also facing the same issue as reported here as well. Go version: vgo version: Getting error:
|
@devanshah2 Why are you using vgo? |
I guess it's just a habit. I have not been working on go releases for a while, but recent changes in the company made me switch to building process. I will have a look into compilation by using go + modules. |
Using it for dependency management instead of |
@devanshah2 In the Go 1.12 release all the features of vgo are available in the normal Go tool, if you set the environment variable GO111MODULE=on. |
@ianlancetaylor Cool. Thanks I will re-try with a clean environment where it is only go installed and no more vgo. |
Tried to compile it with go 1.12 without using vgo
update sys/unix (just in case)
After these steps, all went fine. Without running Upon further investigation it turned out that I already had package "golang.org/x/sys" pinned in go.mod, which was probably causing the issue with go 1.12 when using modules. |
I managed to get around my issue after running:
Then did the |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
Successful build.
What did you see instead?
The text was updated successfully, but these errors were encountered: