-
-
Notifications
You must be signed in to change notification settings - Fork 669
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
cgocall doesn't work #2396
Comments
This is a bug, not specific to your setup. I don't think it's related to #2271. The I'm not exactly sure how the raw files need to be plumbed in, and unfortunately I don't have bandwidth to look into it right now. I'll remove |
@emmaxy I wonder if you could take a look at this issue after #3770 My original hope in #3770 (comment) was to turn on cgocall after your PR is merged. But it seems that Here is an example failure in buildbuddy code base with cgocall turned on
|
What version of rules_go are you using?
0.22.1
What version of gazelle are you using?
0.19.0
What version of Bazel are you using?
2.2.0
Does this issue reproduce with the latest releases of all the above?
Yes.
What operating system and processor architecture are you using?
Mac/Darwin
Any other potentially useful information about your toolchain?
What did you do?
Enabled cgocall analyzer via nogo.
What did you expect to see?
No errors.
What did you see instead?
I received an error that the original go file can't be opened. This is possibly because of #2271.
I'm curious if this is something specific to my setup, or if anyone has gotten this to work. If not, it might make sense to remove cgocall from the "tools_nogo" rule until this is fixed?
The text was updated successfully, but these errors were encountered: