CMake Error Could NOT find CUB (missing: CUB_INCLUDE_DIR)

[shayaknyc]

Hey folks,

Running Garuda Linux and installed the linux-cachyos and linux-cachyos-headers and successfully booted into the linux-cachyos kernel. Attempted to compile the proton-cachyos package via the AUR (https://aur.archlinux.org/packages/proton-cachyos) which lists this repo as the upstream source. When attempting to compile in the arch terminal using makepkg -s after cloning the AUR repo, after a long string, I get this error output:

Re-run cmake no build system arguments
-- The C compiler identification is GNU 14.2.1
-- The CXX compiler identification is GNU 14.2.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /home/user/.cache/paru/clone/proton-cachyos/src/wrappers/i686-pc-linux-gnu-gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /home/user/.cache/paru/clone/proton-cachyos/src/wrappers/i686-pc-linux-gnu-g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Warning (dev) at CMakeLists.txt:25 (find_package):
  Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules
  are removed.  Run "cmake --help-policy CMP0148" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

This warning is for project developers.  Use -Wno-dev to suppress it.

-- Found PythonInterp: /usr/bin/python (found version "3.12.7")
-- Running gen_cmake_skeleton.py
/home/user/.cache/paru/clone/proton-cachyos/src/build/src-kaldi/cmake/gen_cmake_skeleton.py:235: SyntaxWarning: invalid escape sequence '\s'
  libs = re.findall("[^\s\\\\=]+", libs)
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Found CUDAToolkit: /opt/cuda/targets/x86_64-linux/include (found version "12.6.85")
CMake Warning (dev) at CMakeLists.txt:168 (find_package):
  Policy CMP0146 is not set: The FindCUDA module is removed.  Run "cmake
  --help-policy CMP0146" for policy details.  Use the cmake_policy command to
  set the policy and suppress this warning.

This warning is for project developers.  Use -Wno-dev to suppress it.

-- Found CUDA: /opt/cuda (found version "12.6")
-- Found NvToolExt: /opt/cuda/include
CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:233 (message):
  Could NOT find CUB (missing: CUB_INCLUDE_DIR)
Call Stack (most recent call first):
  /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:603 (_FPHSA_FAILURE_MESSAGE)
  cmake/FindCUB.cmake:17 (find_package_handle_standard_args)
  CMakeLists.txt:200 (find_package)


-- Configuring incomplete, errors occurred!
make[1]: *** [../proton-cachyos/Makefile.in:652: /home/user/.cache/paru/clone/proton-cachyos/src/build/.kaldi-configure32] Error 1
make[1]: Leaving directory '/home/user/.cache/paru/clone/proton-cachyos/src/build'
make: *** [../proton-cachyos/Makefile.in:1544: dist] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'proton-cachyos-1:9.0.20241206-2': 
error: packages failed to build: proton-cachyos-1:9.0.20241206-2

I did a little bit of searching for the error Could NOT find CUB (missing: CUB_INCLUDE_DIR) but they were largely related to other Python projects. I did get me into investigating if I need to install the CUB library manually, and discovered that it seems to already be present in /opt/cuda/include/cub on my system. At this stage, not sure how to troubleshoot this, so if anyone has any ideas, I'm all ears!

Thanks in advance!

[ptr1337]

Can you reproduce this issue in a chroot?
e.g docker-makepkg or pkgctl builld ?

[shayaknyc]

Can you reproduce this issue in a chroot? e.g docker-makepkg or pkgctl builld ?

Would love to, but I'm not sure I fully understand what you're asking of me. What path should I be chrooting into? How should I use pkgctl ? Similarly to makepkg -si ?

I'd consider myself advanced beginner/intro intermediate linux user - but I'm no developer, so I'll need a touch more hand-holding.