-
Notifications
You must be signed in to change notification settings - Fork 49
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
HIP build failing with hiprtc related error. #23 (CONT-D) #39
Comments
Hi @jdgh000, sorry for the wait and that this was closed on you. Are you still experiencing this issue? |
I can't reproduce this on ROCm 6.2. Not sure if this was a versioning issue as noted, or if something has changed since this issue was current. I was able to build To clarify what the post you quoted is saying, these two repos have different branches corresponding to different versions of ROCm, so you have to make sure to pull the correct branch for your version of ROCm, as noted in the HIP guide. If you pull branches whose versions do not match, this can cause issues like those you have seen. The HIP guide involves pulling both the HIP and
Replace The I'll close the other issue and leave this one open for now, in case you have any further questions about building HIP and |
Closing this here as well for now. As mentioned, feel free to comment on this issue if you'd like it reopened, or you can submit a new issue. |
THis is continued from following which closed without confirmation: HIP build failing with hiprtc related error. #23
First I want to ask why are you closing without even confirming with me that build works? Build is still failing, please do not close because I cant re-open!!!
Your last post here absolutely makes no sense:
the idea here is, there are two repo you need to build HIP on AMD platforms (there are several but for our purpose we can ignore them).
As I said clr was not building due to hiprtc related error. Are you saying checkout hip and clr, which one to build first?
IF i build clr, it fails with same reason.
The text was updated successfully, but these errors were encountered: