Package Details: rocr-runtime 2.6.0-1

Git Clone URL: https://aur.archlinux.org/rocr-runtime.git (read-only)
Package Base: rocr-runtime
Description: ROCm HSA
Upstream URL: https://github.com/RadeonOpenCompute/ROCR-Runtime
Licenses: unknown
Submitter: farnoy
Maintainer: farnoy
Last Packager: farnoy
Votes: 11
Popularity: 1.609614
First Submitted: 2018-12-21 15:31
Last Updated: 2019-07-14 18:57

Latest Comments

1 2 Next › Last »

kbeckmann commented on 2019-07-11 17:55

Please update the pkgver to 2.6.0. rocm-opencl-runtime depends on this package with that version. If you need this version, you can apply the following patch in the meantime:

diff --git a/PKGBUILD b/PKGBUILD
index 66df78f..c65d41a 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,6 +1,6 @@
 # Maintainer: Jakub Okoński <jakub@okonski.org>
 pkgname=rocr-runtime
-pkgver=2.5.0
+pkgver=2.6.0
 pkgrel=1
 pkgdesc="ROCm HSA"
 arch=(x86_64)
@@ -9,7 +9,7 @@ license=('unknown')
 makedepends=(git cmake gcc ninja)
 depends=('roct-thunk-interface')
 source=("https://github.com/RadeonOpenCompute/ROCR-Runtime/archive/roc-$pkgver.tar.gz")
-sha256sums=("6678bdaf4f6d8ce6e4ed24131f4455c719c0a643c8479f3d69722caa8b4d7187")
+sha256sums=('46636716ef9f222e90cd2f3d54acf9bf50c4088cd55178230628bd195833de88')

 build() {
   mkdir -p "$srcdir/build"

rigred commented on 2019-03-21 12:07

Took me a while to follow up on this. I can confirm it's now working properly again.

Maverick commented on 2019-03-19 00:02

@rigred I had a similar problem with libhsa-runtime64.so linking to libhsakmt.so.2 rather then libhsakmt.so.1. The install was made through trizen. I may have had some older ROCm packages installed which I had deleted later.

I've rebuilt the current rocr-runtime by unpacking and running "makepkg" manually to reproduce the problem and for some reason now it links correctly. Maybe there was some residual in the trizen build directory? o.O Unfortunately I can not reproduce the problem any more..

farnoy commented on 2019-03-18 16:37

Do you have some residuals from another installation? I haven't packaged anything that would provide OpenCL on top of ROCm, so I have no idea why libhsa-runtime64.so would be linked&used.

chrido commented on 2019-03-18 15:15

I get a segfault when I run rocminfo or clinfo. It seems to come from libhsa-runtime64.so.1.

Any hints?

laptop :: ~ » clinfo
[1]    8320 segmentation fault (core dumped)  clinfo
laptop :: ~ » gdb clinfo                                                                                                            139 ↵
GNU gdb (GDB) 8.2.1
(gdb) r
Starting program: /usr/bin/clinfo 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff3b78072 in ?? () from /opt/rocm/hsa/lib/libhsa-runtime64.so.1
(gdb) q

farnoy commented on 2019-03-16 15:16

@ulyssesrr I'm updating all the packages and switching to tarballs instead of git. Thanks for the help.

@rigred I found the issue you experienced. It was because I did not define a parameter they recommend in their README: CMAKE_PREFIX_PATH=/opt/rocm/libhsakmt. I will push the change out soon as it fixes the issue for me:

$ ldd /opt/rocm/bin/rocminfo
    linux-vdso.so.1 (0x00007ffe009fe000)
    libhsa-runtime64.so.1 => /opt/rocm/hsa/lib/libhsa-runtime64.so.1 (0x00007f8b19ada000)
...

ulyssesrr commented on 2019-03-16 02:56

PKGBUILD for 2.2.0: https://gist.github.com/ulyssesrr/508e041cd4c74d0cd0922aa7b9e0fae8

Also added pkgver() to auto track the tag version.

farnoy commented on 2019-03-07 19:14

You're right, there is some issue because when they bumped ROCm version to 2.0, the versions of HSA libs were also renamed to so.2 etc. But this is not the case in official packages, I reported it upstream but the scrips they use to provide official packages are not open source so I'm not exactly sure how they do it.

rigred commented on 2019-03-06 23:02

rocminfo seems to depend on libhsa-runtime64.so.2 which I presume is meant to be included with this. But this package only contains libhsa-runtime64.so.1 and libhsa-runtime64.so.1.1.9

ldd /opt/rocm/bin/rocminfo
        linux-vdso.so.1 (0x00007ffe719f0000)
        libhsa-runtime64.so.2 => not found
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007feb3a6fe000)
        libc.so.6 => /usr/lib/libc.so.6 (0x00007feb3a53a000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007feb3a520000)
        libm.so.6 => /usr/lib/libm.so.6 (0x00007feb3a39b000)
        /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007feb3a8ff000)
pacman -Ql rocr-runtime | grep libhsa
rocr-runtime /opt/rocm/hsa/lib/libhsa-runtime64.so
rocr-runtime /opt/rocm/hsa/lib/libhsa-runtime64.so.1
rocr-runtime /opt/rocm/hsa/lib/libhsa-runtime64.so.1.1.9
rocr-runtime /opt/rocm/lib/libhsa-runtime64.so

Any idea what might be going on? Is this just not packaged right from upstream perhaps?

mardab commented on 2019-01-22 15:19

@farnoy had this package previously installed, so I reinstalled that and now I can continue building miopen, thanks.

Also I see that you are submitting and maintaing all of the related packages, thank You once again and please, continue so.