Bug 2419068 - rocm-validation-suite: FTBFS in EPEL 10.2
Summary: rocm-validation-suite: FTBFS in EPEL 10.2
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: rocm-validation-suite
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Tom.Rix
QA Contact:
URL: https://koschei.fedoraproject.org/pac...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-12-05 03:47 UTC by Orion Poplawski
Modified: 2025-12-05 14:46 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Orion Poplawski 2025-12-05 03:47:58 UTC
Description of problem:
Package rocm-validation-suite fails to build from source in EPEL 10.2.

Version-Release number of selected component (if applicable):
6.4.2-2.el10_2

Steps to Reproduce:
koji build --scratch epel10.2 rocm-validation-suite-6.4.2-2.el10_2.src.rpm

Additional info:
This package is tracked by Koschei. See:
https://koschei.fedoraproject.org/package/rocm-validation-suite


I'm attempting to rebuild rocm-validation-suite for the yaml-cpp 0.8 update in epel10.2-build-side-123884 but it's failing to build with:

+ /usr/bin/cmake -S . -B redhat-linux-build -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_INSTALL_DO_STRIP:BOOL=OFF -DCMAKE_INSTALL_PREFIX:PATH=/usr -DINCLUDE_INSTALL_DIR:PATH=/usr/include -DLIB_INSTALL_DIR:PATH=/usr/lib64 -DSYSCONF_INSTALL_DIR:PATH=/etc -DSHARE_INSTALL_PREFIX:PATH=/usr/share -DLIB_SUFFIX=64 -DBUILD_SHARED_LIBS:BOOL=ON -G Ninja '-DAMDGPU_TARGETS=gfx900;gfx906:xnack-;gfx908:xnack-;gfx90a:xnack+;gfx90a:xnack-;gfx942;gfx950;gfx1010;gfx1012;gfx1030;gfx1031;gfx1035;gfx1100;gfx1101;gfx1102;gfx1103;gfx1150;gfx1151;gfx1152;gfx1153;gfx1200;gfx1201' -DBUILD_FILE_REORG_BACKWARD_COMPATIBILITY=OFF -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_C_COMPILER=/usr/lib64/rocm/llvm/bin/amdclang -DCMAKE_CXX_COMPILER=/usr/lib64/rocm/llvm/bin/amdclang++ -DCMAKE_INSTALL_LIBDIR=/usr/lib64 -DHIP_PLATFORM=amd -DMXDATAGENERATOR_INC_DIR=/builddir/build/BUILD/ROCmValidationSuite-rocm-7.1.0/mxDataGenerator/lib/include -DRVS_BUILD_TESTS=FALSE
CMake Deprecation Warning at CMakeLists.txt:26 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.
  Update the VERSION argument <min> value.  Or, use the <min>...<max> syntax
  to tell CMake that the project requires at least <min> but has been updated
  to work with policies introduced by <max> or earlier.
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
CMake Error at CMakeLists.txt:30 (project):
  The CMAKE_C_COMPILER:
    /usr/lib64/rocm/llvm/bin/amdclang
  is not a full path to an existing compiler tool.
  Tell CMake where to find the compiler by setting either the environment
  variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
  the compiler, or to the compiler name if it is in the PATH.
CMake Error at CMakeLists.txt:30 (project):
  The CMAKE_CXX_COMPILER:
    /usr/lib64/rocm/llvm/bin/amdclang++
  is not a full path to an existing compiler tool.
  Tell CMake where to find the compiler by setting either the environment
  variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
  to the compiler, or to the compiler name if it is in the PATH.
-- Configuring incomplete, errors occurred!
RPM build errors:

I'm not sure what has changed to cause this failure, but koshcei does report a decent amount of dependencies have changed.

Comment 1 Orion Poplawski 2025-12-05 14:42:06 UTC
Ah, I see it now - the epel10 branch was updated to 7.1.0, but was never build.  So - Tom, what's the plan here?  We could revert to 6.4.2 for the rebuild, or are you going to fix the update to 7.1.0 soon?

Comment 2 Orion Poplawski 2025-12-05 14:46:58 UTC
rocm 7.1.0 at least builds for epel10, so perhaps that is a way forward?


Note You need to log in before you can comment on or make changes to this bug.