Hi Cordell, Not sure it will help, but I suppose I could first bump the rocrand package up to 5.2.3 to be consistent with the build chain. It should still be easy to do while we're not in the next stage of the freeze on February 12th. Cordell Bloor, on 2023-01-15: > The rocRAND and hipRAND repos upstream were split after ROCm 5.0, but only > sort-of. The hipRAND repo was moved into a git submodule. Upstream still > builds the two libraries together, just like in ROCm 5.0 (at least for now). > So, perhaps the simplest step would be to make rocrand / hiprand a > multi-upstream tarball repo? There is that, or packaging hipRAND in a side package. Given the affinity between the two, multi-upstream tarball may be the most natural approach in this case. > The upstream hipRAND repo does't have any tags (and therefore getting tarballs > with uscan might be tricky?). If tags would help, I can work with upstream to > get them added retroactively for rocm-5.1.0 and later. Just let me know. For a regular package it would be possible to use git commit IDs instead, but that leads to hard to read version numbers. In the case of MUT, strolling through the example from rocm-hipamd, I see it may be necessary to restrict the version number of the side tarball to be the same as the main source package. So... yes please? :) Have a nice day, :) -- Étienne Mollier <emollier@emlwks999.eu> Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/1, please excuse my verbosity. On air: King Gizzard & The Lizard Wizard - Change
Attachment:
signature.asc
Description: PGP signature