Source: pytorch Version: 2.9.1+dfsg-1~exp1ubuntu2 Followup-For: Bug #1128208
Dear Maintainer, In ubuntu we started building pytorch-rocm that is forked from src:ubuntu but there is something wrong with the configs it seems. It looks like it doesnt build for ROCm at all. See: https://bugs.launchpad.net/ubuntu/+source/pytorch-rocm/+bug/2144078a for more details. I started working on it and saw some bugs/typos already in FindHIP.cmake and FindGloo.cmake files. I also have questions regarding the need of fork for ROCm. Why we are not using build profiles to build for rocm. I started experimenting this and the only conlict I see so far due to gloo-rocm (again forked from src:gloo) I think we could apply the same build profile logic to there as well. I am working on a PoC to see if that works. If it works it will require changes in src:gloo as well. I would like to hear your toughts as well. -- System Information: Debian Release: forky/sid APT prefers resolute APT policy: (500, 'resolute') Architecture: amd64 (x86_64) Kernel: Linux 6.19.0-9-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
