search

ROCm / ROCclr

42 stars 40 forks source link

Installation documentation appears to be out-of-date #34

Open bgamari opened 2 years ago

bgamari commented 2 years ago

The build documentation currently suggests that this package can be built in a standalone manner. However, since https://github.com/ROCm-Developer-Tools/ROCclr/commit/df1449608e92c9e42b4ce5799e6eb51934ae7d4a it appears that this configuration is no longer supported and that it should rather be built as a component of some other unspecified project.

This puts packagers in the difficult situation of knowing that ROCclr is needed yet having no idea of how to actually package it.

saadrahim commented 2 years ago

@mangupta can you share any timelines on a proposed fix to this?

cgmb commented 2 years ago

The documentation should be updated for the benefit of future users, but I can at least tell you how it needs to be done.

ROCclr and hipamd have been built together since ROCm 4.5. (This gist sets lots of unnecessary environment variables, but it provides a simple working example of some of the basic ROCm component builds. They haven't changed since then.)

@Mystro256 and I had a series of discussions with the HIP / ROCclr developers about the path towards a simpler build for HIP, hipamd, ROCclr and the ROCm-OpenCL-Runtime. You can find some of the conclusions from that discussion on the Debian AI mailing list. In short, the tentative plan is to combine the ROCclr, ROCm-OpenCL and hipamd repositories into one repository to reflect the fact that their sources must all be built together.