-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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: problem compiling yubihsm-connector #30784
Comments
Could you please show us the repro steps without |
I'm sorry, I don't know what |
I would be happy to - but, alas, I'm not a The good part of it is - my installation is very close to the standard because I don't know enough to mess with it. The bad part is - I don't even know how to do what you asked for, i.e., how to translate what Here's what the Makefile does:
Both of the env vars referred above are empty. Here's the entire Makefile: If you can tell me what to do/try to help debugging this problem - I'll be happy to do it. |
It does (at least according to its documentation - I probably have even less experience with it than you do) exactly what you suggested is needed - updates the given package, or if So there's no reason that I can see to assume that |
Also, in case it matters - I successfully built this package end of last November, with whatever Go compiler was stable release back then. It doesn't look like the relevant parts of it changed since. |
The problematic changes to golang.org/x/sys/unix were made in December, and were designed to work with Go 1.12. I have used a Darwin system, downloaded yubihsm-connector, installed the gb build tool, run
Building and testing golang.org/x/sys/unix in the usual way, with the Go tool, works fine. OK, I think I may know what is happening. In the Go 1.12 cycle the compiler, assembler, and linker were changed to track the ABI version of assembler symbols; see #27539. As part of making this work, the go tool itself was changed to build an ABI file; see https://golang.org/cl/147257 (some later CLs were also involved). It is likely that |
@ianlancetaylor first, thank you for your effort! In your opinion, is is possible to substitute |
I'm sorry, I don't know the answer to that question. I haven't used gb. I suggest that you ask on the golang-nuts Google Group or in some other forum; see https://golang.org/wiki/Questions. |
@ianlancetaylor thank you. This probably isn't something that One workaround is to adjust the
Then the build would succeed. Perhaps the above would be useful for others. |
A follow-up to/continuation of the prematurely-closed #30777
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
The latest release seems to be the only version where this issue appears.
What operating system and processor architecture are you using (
go env
)?macOS Mojave 10.14.3, Xcode-10.1, current Go package for Mac from https://golang.org, and current
gb
installed following https://getgb.io/docs/install/ instructions.What did you do?
Updated
golang.org/x/sys/unix
package explicitly (after updating everything with--all
), and tried building again withgb build
What did you expect to see?
Successful build.
What did you see instead?
In #30777 you said
Would you mind telling how you suggest doing that, and why in your opinion my update (as shown above) is not sufficient?
The text was updated successfully, but these errors were encountered: