-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Issue]: CMake targets are not fully guarded against multiple inclusion #21
Comments
Thanks for the ticket. This is easily fixed by adding an |
Will the fixed CMake module make it into ROCm 6.2.3 (if there is such a thing) or will it go into ROCm 6.3? Do you want make to create an internal Jira for this? |
This was resolved in a92fa8f |
* Split ABI checks for rocprofiler-sdk-roctx into separate file * Update source/lib/rocprofiler-sdk-roctx/abi.cpp Co-authored-by: Indic, Vladimir <[email protected]> * Update source/lib/rocprofiler-sdk-roctx/abi.cpp Co-authored-by: Indic, Vladimir <[email protected]> * New line --------- Co-authored-by: Jonathan R. Madsen <[email protected]> Co-authored-by: Indic, Vladimir <[email protected]>
Problem Description
Only a subset of the CMake targets in rocprofiler-sdk and rocprofiler-sdk-roctx are guarded against multiple inclusions. The other ROCm packages do not have this issue.
Here is a simple reproducer (CMakeLists.txt):
You will see that having two
find_package(hiprtc)
is OK, but having twofind_package(rocprofiler_sdk)
gives you this error:I believe the problem are these lines in rocprofiler-sdk-targets.cmake:
There are similar issues with the CMake module for rocprofiler-sdk-roctx. You can reproduce the issue by doing
find_package(find_package(rocprofiler-sdk-roctx)
twice in CMakeLists.txtOperating System
Ubuntu 22.04.4 LTS (Jammy Jellyfish)
CPU
AMD EPYC 7713 64-Core Processor
GPU
AMD Instinct MI250
ROCm Version
ROCm 6.2.0
ROCm Component
No response
Steps to Reproduce
No response
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: