-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Investigate why Clang/LLVM UBSan doesn't link #3568
Comments
I'm now seeing this with VS 2022 17.7 Preview 1 and Clang 16:
|
For anyone else running into this issue: I don't get any linker errors when using lld, via |
Not sure if it's the same issue that you're seeing here, but I've been trying to resolve a similar issue and my problem seems to be due to VS shipping with a (presumably custom) version of
|
While merging #3452 (internal MSVC-PR-457627), I had to disable the Clang/LLVM UBSan configurations for the internal test harness, as they fail to link (with linker errors about support machinery). We use Clang/LLVM via an internally captured "NuGet package" with a subset of binaries (but most of the support libs, AFAIK) to avoid excessive space consumption. At the time, I am unsure why UBSan doesn't work in the internal environment. It could be that we need to add more libs to the NuGet package, or it could be due to PATH ordering issues where we're mixing up MSVC and Clang/LLVM's support libs.
Thanks to @zacklj89 for reminding me to file this followup issue instead of being a bad kitty 😼 and silently working around it forever.
The text was updated successfully, but these errors were encountered: