[Issue]: Build - Warnings and errors
@essamROCm ya está trabajando en esto.
Desde el 23/9/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Problem Description
Build should not require rocm supported devices
-- The CXX compiler identification is Clang 24.0.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /opt/rocm-nightly/lib/llvm/bin/amdclang++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- HIP: Using hipcc from relative path: /opt/rocm-nightly/bin/hipcc
CMake Warning (dev) at /opt/rocm-nightly/lib/cmake/hip/hip-config-amd.cmake:82 (message):
GPU_TARGETS was not set, and system GPU detection was unsuccsessful.
The amdgpu-arch tool failed:
Error: 'Failed to get device count: no ROCm-capable device is detected (error code: 100)'
Output: ''
As a result, --offload-arch will not be set for subsequent
compilations, and the default architecture
(gfx906 for dynamic build / gfx942 for static build) will be used
for compiling device code in C++ language mode
Call Stack (most recent call first):
/opt/rocm-nightly/lib/cmake/hip/hip-config.cmake:164 (include)
videoDecode/CMakeLists.txt:57 (find_package)
This warning is for project developers. Use -Wno-dev to suppress it.
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Performing Test HIP_CLANG_SUPPORTS_PARALLEL_JOBS
-- Performing Test HIP_CLANG_SUPPORTS_PARALLEL_JOBS - Success
-- Found rocdecode: /opt/rocm-nightly/include (found suitable version "1.10.0", minimum required is "1.0.0")
-- Found PkgConfig: /usr/bin/pkg-config (found version "1.4.2")
-- Checking for module 'libavcodec'
-- Package 'libavcodec', required by 'virtual:world', not found
-- Checking for module 'libavformat'
-- Package 'libavformat', required by 'virtual:world', not found
-- Checking for module 'libavutil'
-- Package 'libavutil', required by 'virtual:world', not found
-- NOTE: FindFFmpeg failed to find -- FFMPEG
-- Found Python3: /opt/python-shared/cp312-cp312/bin/python3.12 (found suitable version "3.12.9", minimum required is "3.9") found components: Interpreter Development.Module
-- pybind11 v3.1.0
-- Performing Test HAS_FLTO_THIN
-- Performing Test HAS_FLTO_THIN - Success
-- Performing Test HAS_FLTO
-- Performing Test HAS_FLTO - Success
-- rocDecode SDK source warnings remain visible and non-fatal; SDK headers use SYSTEM includes. SDK warnings are not fixed.
-- rocPyVideoDecode target: rocpydecode_3_12
-- rocPyVideoDecode FFmpeg support: OFF
-- rocPyVideoDecode CPU backend support: OFF
-- HIP: Using hipcc from relative path: /opt/rocm-nightly/bin/hipcc
CMake Warning (dev) at /opt/rocm-nightly/lib/cmake/hip/hip-config-amd.cmake:82 (message):
GPU_TARGETS was not set, and system GPU detection was unsuccsessful.
The amdgpu-arch tool failed:
Error: 'Failed to get device count: no ROCm-capable device is detected (error code: 100)'
Output: ''
As a result, --offload-arch will not be set for subsequent
compilations, and the default architecture
(gfx906 for dynamic build / gfx942 for static build) will be used
for compiling device code in C++ language mode
Call Stack (most recent call first):
/opt/rocm-nightly/lib/cmake/hip/hip-config.cmake:164 (include)
jpegDecode/CMakeLists.txt:25 (find_package)
This warning is for project developers. Use -Wno-dev to suppress it.
-- Found rocjpeg: /opt/rocm-nightly/include (found suitable version "1.10.0", minimum required is "1.0.0")
-- rocPyJpegDecode target: rocpyjpegdecode_3_12
-- Configuring done (1.4s)
-- Generating done (0.0s)
-- Build files have been written to: /__w/vision-pack/vision-pack/build/_subprojects/rocpydecode/build
Operating System
ALL
CPU
ALL
GPU
ALL
ROCm Version
ROCm 10.X
Installation Method
Python wheels
Installed ROCm Packages / Versions
Installed ROCm packages / versions
Paste output here
ROCm Component
No response
Steps to Reproduce
No response
(Optional for Linux users) Output of rocminfo --support
rocminfo --support output
Paste output here
Additional Information
No response
- Lenguaje dominante
- C++
- Estrellas
- 8
- Forks
- 13
- Merge medio
- 2 d 10 h
- PR fusionados (30 d)
- 7
Preparar el entorno
Aún no hemos revisado los archivos de configuración de este proyecto. Empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de ROCm/rocPyDecode
-
CMake install: no COMPONENT grouping, Python modules install to lib/ instead of site-packagesPosiblemente ocupada @essamROCm la tomó hace 16 días. Abiertobug enhancement
ROCm/rocPyDecode#285 · 2 comentarios · 1 asignado ·
-
Restructure rocPyDecode into independent video and JPEG binding projectsPosiblemente ocupada @essamROCm la tomó hace 18 días. Abiertoenhancement
ROCm/rocPyDecode#284 · 1 comentario · 1 asignado ·
-
Packaging - Add pinned pybind11 dependency and align dlpack version with rocCV (v1.3) for hermetic buildsPosiblemente ocupada @rrawther la tomó hace 24 días. Abiertoenhancement
ROCm/rocPyDecode#282 · 1 comentario · 2 asignados ·
-
[Issue]: CTest Failure: jpegdecodebatched on AzureCIQuizá libre de nuevo @essamROCm la tomó hace 354 días y no hay ningún pull request abierto. Abiertobug
ROCm/rocPyDecode#256 · 3 comentarios · 1 asignado ·
-
[Issue]: Azure CI - GFX942 FailureQuizá libre de nuevo @AryanSalmanpour la tomó hace 440 días y no hay ningún pull request abierto. Abiertobug help wanted
ROCm/rocPyDecode#224 · 4 comentarios · 3 asignados ·
Todos los issues de ROCm/rocPyDecode
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
sandialabs/seacas#945 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
ROCm/FastFlowLM#757 ·
Los mantenedores suelen responder en 1 día
-
WaterHeaterManagement: tank_percent feature reports wrong feature id (FeatureMap corruption)Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
espressif/esp-matter#1867 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
mltframework/shotcut#1920 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día