https://bugzilla.redhat.com/show_bug.cgi?id=2209759 --- Comment #13 from Philipp K. <philipp-dev@xxxxxxxxxxxxx> --- (In reply to Philipp K. from comment #7) > Ok, sry for the noise, but square.hipref.cpp with the latest build that > include the patches from RHBZ#2207599 work now. However, I find it a bit odd > that this square example pulls in the device libs, even though it is already > compiled and does not use hiprtc. Just for future reference, I opened an issue upstream: https://github.com/ROCm-Developer-Tools/ROCclr/issues/44 However, I dont have much hope that this will get fixed. This should also not block in any way the inclusion of these packages in fedora. However, this probably has the implication that the rocm-hip package requires rocm-device-libs in the spec-file in one way or another? Also rocm-opencl should probably require rocm-device-libs anyway. Maybe rocm-comgr should not require rocm-device-libs only at build time, and pull in rocm-device-libs, which would then satisfy the runtime needs of rocm-opencl and rocm-device-libs? Not sure how realistic this is, but maybe if the aforementioned issue gets resolved, one could in the long-term split off hiprtc as a separate package? At least in theory, I guess, this should allow for binary distribution of dependent packages that only require rocm-hip and do not pull in a full clang/llvm dependency. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component https://bugzilla.redhat.com/show_bug.cgi?id=2209759 _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
