Hi Cory, Cordell Bloor, on 2022-12-02: > ROCm 5.4.0 has released. There are a bunch of fun changes [1], but I'm in no > rush to update. The pain of migrating all the hipamd and comgr patches is > non-trivial and I feel like that effort is better spent elsewhere. > > With that said, there is one updated package that would be nice. The version > of rocm-cmake on Debian Sid is 5.2.3, which predates the fix to respect > CMAKE_INSTALL_LIBDIR. It would be good to bump rocm-cmake to a newer > version. Then all the libraries I'm working on should install to the > appropriate multiarch directory by default. Thanks for the notice, at the moment the Debian release freeze will occur on 2023-01-12, and the ROCm 5.2.3 is in a consistent state in testing, the upcoming Debian 12 bookworm. I feel a bit wary updating to unstable right now, but begun bumping version to 5.4.0 this morning in experimental. If this sounds okay, I'm considering not touching the versions in unstable/testing any more before Debian release, unless there are outstanding issues in the packages of course. That being said, in such context, would it still be worth bumping at least the rocm-cmake version in the unstable and then testing distribution? > I have rocSPARSE, rocFFT and rocThrust packages passing all tests on the > Radeon VII, so next up is symbol tracking and copyright review. Hurrah. Yay! > [1]: https://docs.amd.com/bundle/ROCm-Release-Notes-v5.4/page/ROCm_Math_and_Communication_Libraries.html Have a nice day, :) -- Étienne Mollier <emollier@emlwks999.eu> Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity.
Attachment:
signature.asc
Description: PGP signature