Package Details: rocm-opencl-runtime 2.4.0-1

Git Clone URL: (read-only)
Package Base: rocm-opencl-runtime
Description: ROCm OpenCL™ Compatible Runtime
Upstream URL:
Licenses: MIT
Conflicts: rocm-opencl-git
Provides: opencl-driver, rocm-opencl-runtime
Submitter: ulyssesrr
Maintainer: ulyssesrr
Last Packager: ulyssesrr
Votes: 14
Popularity: 4.141648
First Submitted: 2019-03-17 05:06
Last Updated: 2019-05-11 05:34

Required by (17)

Sources (8)

Latest Comments

1 2 3 4 Next › Last »

artivision commented on 2019-05-22 01:17

Good day, i cannot find image support.

zgalvin commented on 2019-05-21 08:54

@ulyssesrr Same as @Maverick, symlink link to build directory rather then install path.

in the PKGBUILD: ln -s $srcdir/"/opt/rocm/opencl/lib/" "$pkgdir/opt/rocm/opencl/lib/" # not created automatically by ldconfig

maybe link like this: cd "$pkgdir/opt/rocm/opencl/lib/" ln -s x86_64/ # not created automatically by ldconfig

trougnouf commented on 2019-04-30 10:00

conflicts = rocm-opencl-runtime -> unresolvable package conflicts detected

aufkrawall commented on 2019-04-22 17:05

Yes, it provides a driver. You can e.g. check with Luxmark "LuxBall HDR" testscene if it works, it does so for me. Compatibility in general might be very limited though compared to the proprietary driver (which can be used with linux-mainline as well).

ulyssesrr commented on 2019-04-22 17:04

@codibit I've looked the other run-times packages, and it seems most of them do provide "opencl-driver", so I think it won't hurt to add it here. I will be updating the package to 2.3.0 later today and will make it provide opencl-driver.

codibit commented on 2019-04-22 10:14

Maybe this package is providing opencl-driver? There are some packages that require an opencl-driver (davinci-resolve, for instance) and maybe adding the provides key in this package might make installations simpler (if correct, of course :) ).

If instead of depending on opencl-driver I should add another dependency, I would appreciate if someone could tell me which one is correct.

Maverick commented on 2019-03-21 00:54

@ulyssesrr Thank you. For some reason it did link properly on recompile now - no idea what changed. symlink seems to link to build directory rather then install path:

maverick@MavsArch /opt/rocm/opencl/lib % ll
total 69440
drwxr-xr-x 3 root root     4096 Mär 21 01:12 clang
drwxr-xr-x 3 root root     4096 Mär 21 01:12 cmake
-rw-r--r-- 1 root root     2476 Mär 19 01:08 hip.amdgcn.bc
lrwxrwxrwx 1 root root       14 Mär 19 01:08 ->
-rwxr-xr-x 1 root root 26250872 Mär 19 01:08
lrwxrwxrwx 1 root root       83 Mär 19 01:08 -> /home/maverick/builds/rocm-opencl-runtime/src//opt/rocm/opencl/lib/

ulyssesrr commented on 2019-03-20 15:16

@PedroHLC Could you try building with and report back? Naming is different but it's the same package, quite outdated through.

PedroHLC commented on 2019-03-20 15:03

python2-z3 was removed from community following

Any known alternative?

ulyssesrr commented on 2019-03-18 02:12

@VerruckteFuchs and @Nightbane112 Thanks for reporting the wrong path in patch file, I have fixed it in 2.2.0-3. (While incorrect it worked with some AUR helpers and thus eluded my testing)


/opt/rocm/lib/ is part of package rocr-runtime.

/opt/rocm/lib64/ should be part of package roct-thunk-interface.

It seems your rocr-runtime package is not linking properly to your roct-thunk-interface package.

Check the output of ldd /opt/rocm/lib/ and report there. My outputs: