-
Notifications
You must be signed in to change notification settings - Fork 14.8k
[Offload] Fix missing dependency on `clang-nvlink-wrapper' #137033
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
Summary: It's possible that this won't be built in time for the runtimes build. Add this as a dependency. We will also need to make this future proof and loop over all the enabled targets, but that's a later update.
I thought runtime build kicks off at the end of the rest of the build? |
Kind of? There's still explicit dependencies we need since not every target will be built. That's why these already exist. |
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.
This fixes the build for me, thanks. LGTM.
Sorry about that, I didn't notice that this was missing because it's correctly in the |
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.
Fixes the build on the CI/CD too
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/13/builds/6734 Here is the relevant piece of the build log for the reference
|
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/42/builds/4270 Here is the relevant piece of the build log for the reference
|
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/146/builds/2775 Here is the relevant piece of the build log for the reference
|
Summary: It's possible that this won't be built in time for the runtimes build. Add this as a dependency. We will also need to make this future proof and loop over all the enabled targets, but that's a later update.
Summary: It's possible that this won't be built in time for the runtimes build. Add this as a dependency. We will also need to make this future proof and loop over all the enabled targets, but that's a later update.
Summary: It's possible that this won't be built in time for the runtimes build. Add this as a dependency. We will also need to make this future proof and loop over all the enabled targets, but that's a later update.
Summary: It's possible that this won't be built in time for the runtimes build. Add this as a dependency. We will also need to make this future proof and loop over all the enabled targets, but that's a later update.
Summary:
It's possible that this won't be built in time for the runtimes build.
Add this as a dependency. We will also need to make this future proof
and loop over all the enabled targets, but that's a later update.