-
Notifications
You must be signed in to change notification settings - Fork 15.1k
On Windows, in the release build script, fix detecting if clang-cl is in PATH #149597
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
(Sorry for the late review; I was basically offline for the past four weeks.)
Doesn't look like it's auto-merging. Maybe hit the button manually? |
It didn't merge because a test failed. |
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/116/builds/17152 Here is the relevant piece of the build log for the reference
|
/cherry-pick 13391ce |
/pull-request #154399 |
… in PATH (llvm#149597) The checks for detecting if `clang-cl` and `lld-link` are in `%PATH` were wrong. This fixes the comment in llvm#135446 (comment) (cherry picked from commit 13391ce)
The checks for detecting if
clang-cl
andlld-link
are in%PATH
were wrong.This fixes the comment in #135446 (comment)