-
Notifications
You must be signed in to change notification settings - Fork 15.6k
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
undefined link errors on Windows #16844
Comments
This looks like \edit: Yes, adding But the Is the |
We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please add a comment. This issue is labeled |
This is still a problem, it also happens with version 28.0. |
It seems the preprocessor checks we have are not taking into account this particular combination of clang+windows properly. The proposed fix would be to modify |
Ha! You mean like this 😼 ? That works indeed. |
We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please add a comment. This issue is labeled |
We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please reopen it. This issue was closed and archived because there has been no new activity in the 14 days since the |
Still not fixed, please re-open. PR coming up.... @sbenzaquen PR is here: #20025 👀 |
What version of protobuf and what language are you using?
Version: 26.1 / 27.0
Language: C++
What operating system (Linux, Windows, ...) and version?
Windows Server 2022 10.0.20348
What runtime / compiler are you using (e.g., python version or gcc version)
clang version 14.0.6
Target: x86_64-w64-windows-gnu
Thread model: posix
What did you do?
Steps to reproduce the behavior:
I am using Bazel (version 6.5.0) either using a workspace file or using a module (module version
26.0.bcr.1
) and trying to build@com_google_protobuf//:protoc
or@protobuf~26.0.bcr.1//:protoc
respectively.What did you expect to see
The build should succeed.
What did you see instead?
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
Anything else we should know about your project / environment
The text was updated successfully, but these errors were encountered: