Hi Marcel, On 2025-09-26 03:33, Marcel Jira wrote:
Thank you very much for your reply and for looking into this issue!
I have to admit that I don't know much about LLVM, but thanks to your
explanation I now better understand the situation.
My bug report was mainly about two things:
1.
Raising awareness that hipcc ≥ 6.0 is actually needed, even for
"consumer software" like Blender, and therefore an update would be
beneficial. I think that point has been made.
2.
Solving the problem of not being able to use a recent version of Blender
in the way I would like. Regarding this: is there currently a safe way to
update hipcc to ≥ 6.0 without risking system instability? I wouldn’t mind
installing a few packages from sid (or even experimental), but I’d like to
avoid pulling in a large set of dependencies or ending up with an
unbootable system. If it's possible, it might make sense to have some kind
of instructions, also for other users facing this problem.
I hope my questions make sense in the context of this bug report.
My apologies for it taking so long. I was tasked with figuring out how to enable Debian-derived distributions to make use of the AMD Clang fork. It proved to be extremely painful (and greatly delayed my work on updating the runtime). In any case, the HIP Runtime from ROCm 6.4.3 has been uploaded to Debian Unstable and it will be in the Forky repos after the transition has been completed. That should be before the end of the month.
I don't think I should be giving instructions on how to install packages from Unstable on Testing, if only because it requires that you know what you're doing to bail yourself out of any problems you might encounter. If you know enough to handle whatever problems you might create by doing that, you don't need my instructions to do it in the first place.
In any case, it should be on testing soon. Future updates should come faster.
Sincerely, Cory Bloor