Bug#1028957: librocrand-dev: rocrand_INCLUDE_DIR does not exist
Package: librocrand-dev
Version: 5.0.0-2
Severity: normal
X-Debbugs-Cc: cgmb@slerp.xyz
Dear Maintainer,
The CMake integration for the librocrand-dev package appears to be
broken. A call to find_package(rocrand) will fail with an error like:
CMake Error at /usr/lib/cmake/rocrand/rocrand-config.cmake:81 (message):
File or directory //rocrand/include referenced by variable
rocrand_INCLUDE_DIR does not exist !
Call Stack (most recent call first):
/usr/lib/cmake/rocrand/rocrand-config.cmake:97 (set_and_check)
clients/tests/CMakeLists.txt:62 (find_package)
-- Configuring incomplete, errors occurred!
It's not clear to me exactly why this is, but the 5.0.0 version predates
the work done upstream to better support GNUInstallDirs and FHS paths. If
the package were updated to 5.3.3, then d/rules and d/*.install could look
a lot more like the proposed librocsparse-dev package and would probably no
longer have this issue.
The rocRAND and hipRAND repos upstream were split after ROCm 5.0, but only
sort-of. The hipRAND repo was moved into a git submodule. Upstream still
builds the two libraries together, just like in ROCm 5.0 (at least for now).
So, perhaps the simplest step would be to make rocrand / hiprand a
multi-upstream tarball repo?
The upstream hipRAND repo does't have any tags (and therefore getting tarballs
with uscan might be tricky?). If tags would help, I can work with upstream to
get them added retroactively for rocm-5.1.0 and later. Just let me know.
Regards,
Cory Bloor
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-6-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
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 librocrand-dev depends on:
ii librocrand1 5.0.0-2
librocrand-dev recommends no packages.
librocrand-dev suggests no packages.
-- no debconf information
Reply to: