[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1022797: librocm-smi-dev: find_package(rocm_smi) fails due to missing liboam



Package: librocm-smi-dev
Version: 5.2.3-1
Severity: normal

Dear Maintainer,

I was working on packaging rccl when I encountered an error stemming
from find_package(rocm_smi). The text of the error was:

    CMake Error at /lib/cmake/rocm_smi/rocm_smiTargets.cmake:102 (message):
      The imported target "oam" references the file
    
         "/usr/lib/liboam.so.1.0"
    
      but this file does not exist.  Possible reasons include:
    
      * The file was deleted, renamed, or moved to another location.
    
      * An install or uninstall procedure did not complete successfully.
    
      * The installation package was faulty and contained
    
         "/lib/cmake/rocm_smi/rocm_smiTargets.cmake"
    
      but not all the files it references.
    
    Call Stack (most recent call first):
      /lib/cmake/rocm_smi/rocm_smi-config.cmake:53 (include)
      CMakeLists.txt:282 (find_package)
    
    
    -- Configuring incomplete, errors occurred!

If you look through rocm_smiTargets.cmake, you can see that the
librocm-smi-dev package is creating CMake targets that refer to liboam.

As a workaround, I added liboam-dev directly to the rccl build-depends
and installed the package manually. This resolved the problem. However,
it seems to me that either rocm_smi should not be exporting the oam
target or librocm-smi-dev should depend on liboam-dev. I'm not sure
which option would be better.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-2-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages librocm-smi-dev depends on:
ii  librocm-smi64-1  5.2.3-1

librocm-smi-dev recommends no packages.

librocm-smi-dev suggests no packages.

-- no debconf information


Reply to: