Arch Linux User Repository

Following changes for 19.20 at the right places in the PKGBUILD, maybe works. Didn't work for me. Built the package, but segfault.

pkgver='19.20.812932'

major='19.20'

minor='812932'

sha256sums=('c5376760ce15454c5ef5cef86571f3806114403d91b8a210629d2e927c98d852')

And a small suggestion: add a "-p" to all mkdir commands. This prevents from fail: directory exists when rebuilding a package.

@grmat, ok, thanks for explanation. But I think you may remove it now, as it is a bit confusing and anyway it was done several years ago, so no one affected person remaining I think. In readme there is no info that you said (about that you done it for co-existance of both versions), so I suggest you to place it there and also remove amdgpocl mentioning.

@Ashark: amdgpocl was the name I've been using for this package before this opencl-amd, which suits the arch package names better. The closed driver includes another version of the libdrm. The free one doesn't contain all the functionality and is more frequently updated. The renaming is a workaround to be able to use the free libdrm with the free stack alongside this one with opencl-amd. See readme for more info

@francoism90: if clover (mesa) works for you, I'd prefer that. E.g. It doesn't for cycles (blender). The two don't conflict as they both use icd

@grmat can you please explain why this package conflicts with amdgpocl? I cannot see any package providing that. And why do you rename libdrm_amdgpu to libdrm_amdgpo? Edit: I explored a git history of this package and saw that it was named amdgpocl previously. Then it needed to use replaces instead of conflicts array. I think it could be removed now. And amdgpO naming was done sinse initial commit, I still do not understand why.

Well, I haven't benchmarked, but it did offer actually-working-with-blender-benchmark, which I've since learned does very bad things, being pre-2.79 Blender.

Also, this OpenCL runtime causes DaVinci Resolve to crash on startup, I haven't tested if installing opencl-mesa fixes that yet, since I got so pissed at it crashing once again that I uninstalled it and deleted the download package.

Any benchmark available against opencl-mesa? It doesn't seem to conflict either, does this package offer any features not provided with the open-source one?

Here is an updated PKGBUILD, with the current version included in the revision history for comparison:

https://gist.github.com/kode54/51ae68590ac4b2cd5c4ce85c0d71a3a3

@Olympus593 How do I append a null kernel to individual programs? I'm not sure what this means exactly.

@grmat same copy to host problem on SI and CI cards. The only known workaround is by appending a null kernel but it can only work for individual programs