Hi Christian, On 2025-05-05 14:05, Christian Kastner wrote:
the HIP flavor build of ggml takes a long time, which makes iterating on package development cumbersome, especially since the things I'm working on are entirely unrelated to HIP. I added a package-local build profile [1] so that this can be skipped easily. However, I think it would make more sense to register an official build profile for this [2], something like 'norocm', so that this same pattern can be applied globally to other packages as well.
I'm no expert, but that seems consistent with other build profiles. I don't have any particular concerns. It obviously won't always be applicable.
However, the biggest reason why ROCm-enabled packages take so long to build is that they're being built a dozen times in order to cover all GPU architectures. When working on HIP-enabled packages, I often trim the GPU targets list down to a single GPU until I'm ready for my final test. I wonder if perhaps we could solve this problem by providing a centralized way to specify the HIP build targets and create a standard way to override them. A few developers have expressed the need for something like that anyway, most recently with regards to spfft [1].
An organized way of handling the GPU build targets would help to solve this problem not only for package that have an optional ROCm component, but also for packages that are ROCm-specific. That includes both the ROCm libraries themselves and rdepends like magma-rocm.
Sincerely, Cory Bloor[1]: https://salsa.debian.org/science-team/spfft/-/merge_requests/1#note_593022