1. 1
2. 2
3. 3
4. 4
5. 5
6. 6
7. 7
8. 8
9. 9
10. 10
11. 11
12. 12
13. 13
14. 14
15. 15
16. 16
17. 17
18. 18
19. 19
20. 20
21. 21
22. 22
23. 23
24. 24
25. 25
26. 26
27. 27
28. 28
29. 29
30. 30
31. 31
32. 32
33. 33
34. 34
35. 35
36. 36
37. 37
38. 38
39. 39
40. 40
41. 41
42. 42
43. 43
44. 44
45. 45
46. 46
47. 47
48. 48

# ROCm for Arch Linux
This repository hosts a collection of [Arch Linux](https://www.archlinux.org/) [PKGBUILDs](https://wiki.archlinux.org/index.php/PKGBUILD) for the [AMD ROCm Platform](https://rocmdocs.amd.com/en/latest/).
These scripts implement a great portion of the stack, ranging from low-level interfaces, over compilers to high-level application librariers.

## Installation
The Arch Linux packages for ROCm are available on the [AUR](https://wiki.archlinux.org/index.php/Arch_User_Repository).
Since many packages will be installed, it is recommended to use an [AUR helper](https://wiki.archlinux.org/index.php/AUR_helpers)
like [`yay`](https://aur.archlinux.org/packages/yay/).

It is also recommended to use the [`arch4edu`](https://wiki.archlinux.org/index.php/Unofficial_user_repositories#arch4edu) binary repository as it will
greatly speed up your installation time.
For directions see [Add arch4edu to your Archlinux](https://github.com/arch4edu/arch4edu/wiki/Add-arch4edu-to-your-Archlinux).

To install ROCm, use
```bash
yay -S rocm-hip-sdk rocm-opencl-sdk
```
which includes the low-level components and compilers, utilities like `rocminfo` and GPU-accelerated math libraries. See the [documentation](https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation_new.html#packages-in-rocm-programming-models) for an overview on the available meta packages.
> **WARNING** It is strongly recommended to remove all ROCm components when updating to a new release.
> Otherwise, building the packages with `yay` may have unwanted side effects resulting in build errors.
> If it's a small release with only a few updated packages, consider building them in a [clean chroot](https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot).
>
> One way to mitigate these issues is to use the binary versions of the packages provided by arch4edu.

You can also install specific ROCm packages like so:
```bash
yay -S rocminfo
```

For additional installation configuration, such as adding a user to the `video`
group, we refer to AMD's [installation guide](https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html).

To uninstall, use the following command:
```bash
yay -R rocm-hip-sdk rocm-opencl-sdk
```

For more helpful tips see the ArchWiki entry on ROCm, [here](https://wiki.archlinux.org/index.php/GPGPU#ROCm).

## Contributing
Your contribution is always welcome. Use the [issue tracker](https://github.com/rocm-arch/rocm-arch/issues) to report problems with the AUR packages.
Optimally, you open a pull request that solves your problem.
For most packages, you have to update `pkgver` and `sha256sums`. Before you commit your changes you will need to generate `.SRCINFO` from the updated `PKGBUILD`:
```bash
makepkg --printsrcinfo > .SRCINFO
```
and add it to your commit.
As we want to bring ROCm into `community` we would greatly appreciate if you test that the package builds in a [clean chroot](https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot).