From: Jipok <Jipok@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [Package Request] ROCM Packages
Date: Tue, 12 Sep 2023 19:00:06 +0200 [thread overview]
Message-ID: <20230912170006.OXEeMW0C3pBUUfM4cDhWgJ58awiUzujykX2GKHRogi0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26415@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2249 bytes --]
New comment by Jipok on void-packages repository
https://github.com/void-linux/void-packages/issues/26415#issuecomment-1702991439
Comment:
Well, for those who, like me, want to build, I will leave a hint just in case. I warn you that this will take a lot of time (a day) and require a lot of vram+swap(up to 60GB)
```bash
sudo xbps-install -Su
git clone https://github.com/rederick29/void-packages rocm
cd rocm
git checkout rocm
git remote add upstream https://github.com/void-linux/void-packages
git fetch upstream master
git rebase upstream/master
./xbps-src binary-bootstrap
# REMOVE the '~' (tilde) from the GPU architecture(s) you wish to build for
echo "XBPS_PKG_OPTIONS=~gfx803,~gfx900,~gfx906,~gfx908,~gfx90a,~gfx1010,~gfx1011,~gfx1012,~gfx1030,~gfx1031,~gfx1100,~gfx1101,~gfx1102" >> etc/conf
./xbps-src pkg HIP-sdk
```
**UPD:** Faster way:
```bash
git clone https://github.com/rederick29/void-packages rocm --depth 1 -b rocm
git clone --depth 1 https://github.com/void-linux/void-packages
cp -r rocm/srcpkgs/{FunctionalPlus,HIP-sdk,HIPIFY,MIOpen,MIOpenGEMM,ROCR-Runtime,ROCT-Thunk-Interface,ROCclr,ROCdbgapi,ROCgdb,ROCm-CompilerSupport,ROCm-Device-Libs,ROCm-OpenCL-Runtime,ROCm-composable_kernel,ROCm-core,frugally-deep,half,hipBLAS,hipCUB,hipFFT,hipSOLVER,hipSPARSE,hipamd,hsa-amd-aqlprofile-bin,magma,python3-CppHeaderParser,python3-barectf,rccl,rocALUTION,rocBLAS,rocFFT,rocMLIR,rocPRIM,rocRAND,rocSOLVER,rocSPARSE,rocThrust,rocm-cmake,rocm-flang-pgmath,rocm-flang,rocm-llvm-openmp,rocm-llvm,rocm_smi_lib,rocminfo/,rocprofiler,rocprofiler-v2,roctracer} ./void-packages/srcpkgs/
# Go to https://github.com/void-linux/void-packages/compare/master...rederick29:void-packages:rocm
# Copy additions from common/shlibs and paste at end of ./void-packages/common/shlibs
cd void-packages
./xbps-src binary-bootstrap
./xbps-src pkg rocminfo
sudo xi rocminfo
# Get GPU architecture name:
/opt/rocm/bin/rocminfo
# REMOVE the '~' (tilde) from the GPU architecture(s) you wish to build for:
"XBPS_PKG_OPTIONS=~gfx803,~gfx900,~gfx906,~gfx908,~gfx90a,~gfx1010,~gfx1011,~gfx1012,~gfx1030,~gfx1031,~gfx1100,~gfx1101,~gfx1102" >> etc/conf
# Build what you want. For all packages:
./xbps-src pkg HIP-sdk
```
next prev parent reply other threads:[~2023-09-12 17:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 21:07 [ISSUE] " 0x0f0f0f
2020-11-16 21:24 ` [Package Request] " 0x0f0f0f
2022-11-02 12:25 ` TeddyDD
2023-02-26 20:29 ` Nicop06
2023-02-27 9:24 ` TeddyDD
2023-02-27 9:24 ` TeddyDD
2023-06-02 12:15 ` rederick29
2023-06-02 12:37 ` rederick29
2023-08-27 19:53 ` Jipok
2023-08-31 14:12 ` Jipok
2023-08-31 14:21 ` rederick29
2023-08-31 14:24 ` rederick29
2023-08-31 15:19 ` Jipok
2023-09-01 16:09 ` Jipok
2023-09-01 18:06 ` Jipok
2023-09-10 22:20 ` Jipok
2023-09-10 22:25 ` Jipok
2023-09-12 17:00 ` Jipok [this message]
2023-09-15 3:54 ` itsdeadguy
2023-09-15 3:57 ` classabbyamp
2023-09-16 15:32 ` Jipok
2024-04-03 10:59 ` Jipok
2024-04-03 11:03 ` Jipok
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230912170006.OXEeMW0C3pBUUfM4cDhWgJ58awiUzujykX2GKHRogi0@z \
--to=jipok@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).