Public bug reported:

Trying to use the CMake config file of rocALUTION in downstream projects
fails with an error like the following:

CMake Error at 
/usr/local/share/cmake-3.30/Modules/CMakeFindDependencyMacro.cmake:76 
(find_package):
  By not providing "FindHIP.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "HIP", but
  CMake did not find one.

  Could not find a package configuration file provided by "HIP" with any of
  the following names:

    HIPConfig.cmake
    hip-config.cmake

  Add the installation prefix of "HIP" to CMAKE_PREFIX_PATH or set "HIP_DIR"
  to a directory containing one of the above files.  If "HIP" provides a
  separate development package or SDK, be sure it has been installed.
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/rocalution/rocalution-config.cmake:90 
(find_dependency)
  CMakeLists.txt:232 (FIND_PACKAGE)

This is because that CMake config file is looking for a HIP package even
if rocALUTION was built without support for HIP.

The following upstream change fixes the generation of the CMake config file:
https://github.com/ROCm/rocALUTION/commit/a7cdd397f1a293fe8fab2082e6e6aa13ac4af640

Would it be possible to cherry-pick that change for the package that is
distributed by Ubuntu?

Thank you.
Markus

** Affects: rocalution (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

- When trying to use the CMake config file of rocALUTION in downstream
- projects fails with an error like the following:
+ Trying to use the CMake config file of rocALUTION in downstream projects
+ fails with an error like the following:
  
  CMake Error at 
/usr/local/share/cmake-3.30/Modules/CMakeFindDependencyMacro.cmake:76 
(find_package):
-   By not providing "FindHIP.cmake" in CMAKE_MODULE_PATH this project has
-   asked CMake to find a package configuration file provided by "HIP", but
-   CMake did not find one.
+   By not providing "FindHIP.cmake" in CMAKE_MODULE_PATH this project has
+   asked CMake to find a package configuration file provided by "HIP", but
+   CMake did not find one.
  
-   Could not find a package configuration file provided by "HIP" with any of
-   the following names:
+   Could not find a package configuration file provided by "HIP" with any of
+   the following names:
  
-     HIPConfig.cmake
-     hip-config.cmake
+     HIPConfig.cmake
+     hip-config.cmake
  
-   Add the installation prefix of "HIP" to CMAKE_PREFIX_PATH or set "HIP_DIR"
-   to a directory containing one of the above files.  If "HIP" provides a
-   separate development package or SDK, be sure it has been installed.
+   Add the installation prefix of "HIP" to CMAKE_PREFIX_PATH or set "HIP_DIR"
+   to a directory containing one of the above files.  If "HIP" provides a
+   separate development package or SDK, be sure it has been installed.
  Call Stack (most recent call first):
-   /usr/lib/x86_64-linux-gnu/cmake/rocalution/rocalution-config.cmake:90 
(find_dependency)
-   CMakeLists.txt:232 (FIND_PACKAGE)
+   /usr/lib/x86_64-linux-gnu/cmake/rocalution/rocalution-config.cmake:90 
(find_dependency)
+   CMakeLists.txt:232 (FIND_PACKAGE)
  
  This is because that CMake config file is looking for a HIP package even
  if rocALUTION was built without support for HIP.
  
  The following upstream change fixes the generation of the CMake config file:
  
https://github.com/ROCm/rocALUTION/commit/a7cdd397f1a293fe8fab2082e6e6aa13ac4af640
  
  Would it be possible to cherry-pick that change for the package that is
  distributed by Ubuntu?
  
  Thank you.
  Markus

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2082246

Title:
  Using CMake config file fails because of missing HIP package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rocalution/+bug/2082246/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to