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
crypto: "error Never include this file directly. Use <lzma.h> instead." during test #25240
Comments
@dlsniper can we tell what version of I don't have a |
Unfortunately, I cannot. However, I asked the user about this: https://youtrack.jetbrains.com/issue/GO-5653#comment=27-2855172 |
I get same error when I copy Applications from one Macbook to another , maybe the copy that overlay the "/usr/local/include" dir , so move it and use global librarys . and try again |
I have same issue too. |
sudo mv /usr/local/include /usr/local/include_old |
@cc14514 This solved my issue. Thank you so much :) |
Why doesn't Apple's migration assistant take care of something like this???? Thank you for posting. |
cc @FiloSottile several users seem to be running into this, but I'm not sure what Go could do. |
@cc14514 How did you know about this solution? It has been bothering me for a long time. thank you very much. |
Thanks, solved my issues too! |
Works perfectly! Just migrated to my new machine and came across the issue when I ran a Swift script. Thanks again. |
Worked perfectly! Thanks @cc14514 |
In case you don't want to mess with the whole |
I'm glad to help you. |
you are welcome, It's been bothering me for a long time too. |
It helped me a lot, thanks very much. |
The crypto/x509 darwin cgo code was deleted entirely only the other day in CL 232397. That will be part of go1.16 so this issue should be fixed now for the next release. |
Yay! |
Hi,
We just got the following report, https://youtrack.jetbrains.com/issue/GO-5653, on our issue tracker but I believe this is a Go issue.
By the looks of it, the user is using at least Go 1.10 on a macOS. I suspect this has something to do with the fact that we force Go to compile the test binary with
-gcflags="all=-N -l"
in order to improve the debugging experience for the users.Thank you.
The text was updated successfully, but these errors were encountered: