Package Details: hipsycl-rocm-git r500.5f30bc1-1

Git Clone URL: (read-only, click to copy)
Package Base: hipsycl-rocm-git
Description: Implementation of SYCL 1.2.1 over AMD HIP/NVIDIA CUDA
Upstream URL:
Licenses: BSD
Provides: hipsycl, hipsycl-rocm, sycl
Submitter: illuhad
Maintainer: illuhad (acxz)
Last Packager: acxz
Votes: 4
Popularity: 0.004755
First Submitted: 2018-09-29 00:57
Last Updated: 2020-03-24 21:17

Pinned Comments

acxz commented on 2020-03-24 17:47

Development is on Github: Please open issues and PRs there instead of commenting.

Latest Comments

acxz commented on 2020-03-24 17:47

Development is on Github: Please open issues and PRs there instead of commenting.

acxz commented on 2020-03-02 20:04

@illuhad thanks for your detailed response. As of right now my focus is getting the ROCm stack working on Arch via the AUR, once we get that working I will later shift to focusing on hipsycl and the related packages. I would like to eventually get the hipsycl installation working via the AUR and when that time comes I will definitely contact you (and ask to be (co)maintainer)), but not before we get a working stack. Thank you!

illuhad commented on 2020-03-01 21:21

@acxz I agree that it is desirable to have hipSYCL packages in the AUR for visibility. However, I think integrating our PKGBUILD with the AUR is going to be difficult. The reason is that we want to offer a hierarchy of installation mechanisms:

  • singularity container images for users who just want to have something that works
  • install scripts for users that use a distribution that we do not provide packages for, or want to have more control over the installation
  • binary packages and repositories
  • All of this for a variety of distributions.

In order to keep the maintenance effort for us as low as possible, the packaging process builds a singularity container image for the target Linux distribution, installs hipSYCL using the installation scripts to /opt/hipSYCL and then just packages this existing installation (e.g. using a PKGBUILD on Arch). This makes it difficult to integrate with the AUR, outside of our packaging pipeline. Additionally, we also build our packages against our own LLVM distributions such that we can verify functionality before shipping packages (hipSYCL imposes certain requirements on the way LLVM is compiled - for most distributions, this is not a problem though).

If you want, you can have a look at our stuff here:

If you want to create a PKGBUILD for the AUR, I will support you of course (you can become maintainer of this package here if you like) but at the moment we lack the manpower to support hipSYCL from our side on distribution specific platforms like the AUR, in particular because all distributions have different guidelines etc that need to be obeyed for this.

If you want to discuss how this should be done in more detail, I invite you to open an issue on github :)

acxz commented on 2020-02-29 04:58

@illuhad, is there any way to upload the package PKGBUILD's to the AUR. This makes them more visible and better integrated with the rest of the Arch AUR. Some of us (naetherm, neeshy, and me) have started a concentrated effort in bringing the ROCm and HIP related packages up to date on Arch here: and I would eventually like to build hipsycl against these ROCm packages. Also posting the PKGBUILDs here makes it easier for Arch Trusted Users to pull them from the AUR into the main repos, which should be the end goal of any package on the AUR.

illuhad commented on 2020-02-12 21:55


the hipSYCL project provides an Arch Linux package repository with packages for the entire stack, including ROCm.

see for more information.

we recommend using our packages instead of this pkgbuild, as this is where we will focus our maintenance efforts on.

pix3l commented on 2020-02-12 18:29


Has anybody uploaded rocm packages to some repo?

Meteorhead commented on 2020-02-02 11:41

The package fails to build on a minty fresh install of Manjaro 18. Upon trying to install from the stock Pacman GUI, I get this error in the build logs:

[ 65%] Building CXX object src/libhipSYCL/CMakeFiles/hipSYCL_cpu.dir/queue.cpp.o
cd /var/tmp/pamac-build-mnagy/hipsycl-rocm-git/src/hipSYCL/build/src/libhipSYCL && /var/tmp/pamac-build-mnagy/hipsycl-rocm-git/src/hipSYCL/bin/syclcc-clang  -DHIPSYCL_DEBUG_LEVEL=1 -DhipSYCL_cpu_EXPORTS -I/var/tmp/pamac-build-mnagy/hipsycl-rocm-git/src/hipSYCL/include -I/var/tmp/pamac-build-mnagy/hipsycl-rocm-git/src/hipSYCL/contrib/hipCPU/include  -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -O3 -DNDEBUG -fPIC   --hipsycl-platform=cpu --hipsycl-bootstrap --hipsycl-config-file=/var/tmp/pamac-build-mnagy/hipsycl-rocm-git/src/hipSYCL/build/syclcc.json -std=c++14 -o CMakeFiles/hipSYCL_cpu.dir/queue.cpp.o -c /var/tmp/pamac-build-mnagy/hipsycl-rocm-git/src/hipSYCL/src/libhipSYCL/queue.cpp
clang-9: error: no such file or directory: 'hip.amdgcn.bc'
clang-9: error: no such file or directory: 'opencl.amdgcn.bc'

Plus hordes of other .bc files missing. Is there a missing dependency on the package? Are build flags wrong?

illuhad commented on 2019-07-14 09:57

Does it stop because of missing CUDA? I would expect it to mention that it cannot find CUDA, but not to stop the compilation. The reason it does that is that it tries to enable any backends that it can, so if CUDA were installed as well it would also automatically enable the CUDA backend. That's why it checks if there's CUDA installed.

steinbuch commented on 2019-05-14 20:34

I have an AMD GPU and so only ROCm. Do you why this hipsycl version still complains about missing CUDA?