Hi Tom, Rix, Tom, on 2025-07-16: > Perhaps this is a known issue, related to the gpu set that the stack is built for, the auto check rule will fire when /dev/kfd is detected > Like https://salsa.debian.org/rocm-team/hipfft/-/blob/debian/unstable/debian/rules#L31 > With all of the APU's out there, like with my build machine, a gfx1103, this rule fires but without having built for the gfx1103 target, this check is meaningless. Is there a way to improve the logic to either opt in or check the running matches the building gpu? On fedora we use an opt in for testing while building. I would say the Debian centric approach to run the build with profile "nocheck" to make sure that the test suite is not kicking, no matter what. This is materialise by the check earlier in the recipe[2] you pointed to. This can be passed via sbuild argument --profiles you're using sbuild, or via "make" variable DEB_BUILD_OPTIONS for hand crafted builds. [2]: https://salsa.debian.org/rocm-team/hipfft/-/blob/debian/unstable/debian/rules#L29 In hope this helps, :) -- .''`. Étienne Mollier <emollier@debian.org> : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from my alarm clock `-
Attachment:
signature.asc
Description: PGP signature