dev-util/therock-bin
ROCm SDK pre-built distribution from TheRock (AMDGPU_TARGETS-selected)
Screenshots
-
therock-bin-7.14.0-r2~amd64amdgpu_targets_gfx1030 amdgpu_targets_gfx1100 amdgpu_targets_gfx1101 amdgpu_targets_gfx1102 amdgpu_targets_gfx1103 amdgpu_targets_gfx1150 amdgpu_targets_gfx1151 amdgpu_targets_gfx1152 amdgpu_targets_gfx1153 amdgpu_targets_gfx1200 amdgpu_targets_gfx1201 amdgpu_targets_gfx908 amdgpu_targets_gfx90a amdgpu_targets_gfx942 amdgpu_targets_gfx950 python_single_target_python3_12 python_single_target_python3_13 python_single_target_python3_14
View 
Download 
Browse License: MIT BSD Apache-2.0 UoI-NCSA Boost-1.0 Overlay: stuff -
therock-bin-7.13.0~amd64amdgpu_targets_gfx1030 amdgpu_targets_gfx1100 amdgpu_targets_gfx1101 amdgpu_targets_gfx1102 amdgpu_targets_gfx1103 amdgpu_targets_gfx1150 amdgpu_targets_gfx1151 amdgpu_targets_gfx1152 amdgpu_targets_gfx1200 amdgpu_targets_gfx1201 amdgpu_targets_gfx908 amdgpu_targets_gfx90a amdgpu_targets_gfx942 amdgpu_targets_gfx950 python_single_target_python3_12 python_single_target_python3_13
View Download Browse License: MIT BSD Apache-2.0 UoI-NCSA Boost-1.0 Overlay: stuff
ChangeLog
commit cb9d738326b1e31b5e659e0966c372529274a29b
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Aug 17 00:29:35 2026 +0200
dev-util/therock-bin: use virtual zlib provider
The binary needs the zlib ABI rather than a specific implementation. Depend on
virtual/zlib so compatible providers satisfy it without retaining the deprecated
concrete atom.
commit add5779373854b6ddbbade28bca06e5997c8ae5c
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Aug 16 17:32:30 2026 +0200
dev-util/therock-bin: add runtime deps to 7.13.0
The exact AMD payload declares Perl, Python 3, and zlib as required dependencies. Its
installed tree contains corresponding scripts and libz consumers, while its versioned
Python payload stops at 3.13.
commit 72b2759e9fda3a8dc239a14a3f738183ed530ea0
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Aug 16 16:42:35 2026 +0200
dev-util/therock-bin: drop 7.14.0-r1
AMD removed installer build 6 from the canonical release endpoint, leaving this
revision unfetchable. Build 7 supersedes it without changing the upstream ROCm
release version.
commit 6d0d25688db7535ba9f33afda83af4bd69269844
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Aug 16 16:42:03 2026 +0200
dev-util/therock-bin: add 7.14.0-r2
AMD replaced installer build 6 with build 7 at the canonical release endpoint. The
replacement payload also exposes direct Perl, Python, and zlib runtime requirements
that must not depend on incidental system packages.
commit ff6c42c265a8d760643f299305032f65db77be06
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 11:57:08 2026 +0200
dev-util/therock-bin: follow the 7.14.0 installer reissue to -6, revbump
AMD reissued the runfile and withdrew the previous one:
rocm-installer-7.14.0-5.run now 404s at repo.radeon.com while -6 serves.
The package could not be fetched at all as shipped, so this is a broken
fetch rather than a version being merely stale. PV is unchanged, which
is why MY_BUILD exists and why this is a revbump.
Re-checked the payload rather than assuming a reissue keeps its shape,
since the ebuild slices the tar out of the runfile by hand. The
structure holds: filesizes/offset arithmetic still finds the archive,
BUILDINFO still reports ROCm 7.14.0 (package version 7.14.0rc3),
component-rocm/content-base.tar.xz is present, and the same eight
content-gfx families ship -- gfx103x, gfx110x, gfx115x, gfx120x,
gfx908, gfx90a, gfx94x, gfx950 -- so AMDGPU_ARCHS still maps onto real
components.
The two revisions are close in size, 5.46 GiB each, consistent with a
reissue rather than a rebuild.
commit f998d8b358f078daf3bb7e098f2081c3a63d93bf
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 11:54:43 2026 +0200
dev-python/vllm: drop the orphaned f5bc33c flash-attn patch
Each flash-attn patch is named for the commit the ebuild pins, since
the filename is built from $. f5bc33c was pinned by
0.21.0, which is no longer in the tree, and nothing else references it
-- the only occurrence of the hash anywhere is inside the patch's own
diff header.
The four live pins each still have their patches: bce2942 for 0.22.1,
dd62dac for 0.23.0 and 0.24.0, 2c839c3 for 0.25.x and caaa4eb for
0.26.0.
commit d3638af0135e0fc98e4e03162e9778de73a73323
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jul 16 14:39:33 2026 +0200
dev-util/therock-bin: add 7.13.0
Packaged from rocm-installer-7.13.0-3.run the same way as 7.14.0, and kept
alongside it. sci-ml/lemonade pins ROCm 7.13.0 for its rocm-stable backend
and reuses a system ROCm only on a major.minor match, so a 7.13.0 tree
(/opt/therock-bin/.info/version = 7.13.0) is what lemonade's USE=system-therock
points lemond at; 7.14.0 stays for general newest-ROCm use.
7.13's runfile differs structurally from 7.14's: the gfx115x arches ship as
separate per-arch content tarballs (content-gfx1150/1151/1152, no gfx1153), so
_therock_family maps each to its own tarball while the rest stay coarse
families. Internally 7.13.0rc2 (VERSION), no BUILDINFO.
commit 0d0489459653c936c2e23220f8e3b11e2b6285d0
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jul 16 13:05:55 2026 +0200
dev-util/therock-bin: repackage from the 7.14.0 release runfile
AMD ships the ROCm 7.14.0 release only as a Makeself runfile installer
(rocm-installer-7.14.0-5.run) -- there is no per-arch release tarball. The
therock-dist-linux-*.tar.gz form exists as nightly a<DATE> snapshots only,
the therock-X.Y GitHub releases carry no assets, and the source tag is just
TheRock's build system. Drop the two nightly snapshot ebuilds and package the
release itself:
- SRC_URI is the .run (Makeself 2.4.2, COMPRESS=none). src_unpack slices the
uncompressed tar payload out by offset (file size minus the header's
filesizes var; stat -L since portage symlinks the distfile) without running
the installer, then extracts component-rocm/content-base.tar.xz plus the
selected arch's content-gfx<family>.tar.xz.
- src_install flatten-merges each component's rocm/core-7.14 subtree into
/opt/therock-bin. The libraries are $ORIGIN-rpath relocatable, so no
patchelf, keeping the ROCM_PATH=/opt/therock-bin runtime model.
- IUSE moves to the release's fine-grained amdgpu_targets (the gfx110x/115x/
120x members plus gfx1030/gfx908/gfx90a/gfx942/gfx950); the release drops
the gfx900/gfx906/gfx101x that the nightly carried.
The .run is internally 7.14.0rc3 build -5 but is the official 7.14.0 release;
MY_BUILD tracks the installer revision for a rebuild.
commit e449031d82a8aeb615ee2c8f3b546446e708ccb0
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Jun 20 12:07:50 2026 +0200
dev-util/therock-bin: drop 7.14.0_alpha20260604
commit a9cb82bf6fd696bac63033b1605ac200087524b7
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Jun 20 12:07:50 2026 +0200
dev-util/therock-bin: add 7.14.0_alpha20260612
commit b808b79b04aa887e34b891b3c8b70cc27e8dcb41
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jun 11 14:56:51 2026 +0200
dev-util/therock-bin: drop 7.14.0_alpha20260528
commit b347871109e95b6d223c9ce0994896f41dad5b43
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jun 11 14:56:07 2026 +0200
dev-util/therock-bin: add 7.14.0_alpha20260611
commit df145c795a85b4d34d2b92359b984483b7c039ee
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jun 4 16:38:01 2026 +0200
dev-util/therock-bin: drop 7.14.0_alpha20260520
commit 3f2af3009223025fb8cea3c54d37915c7949ed1e
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jun 4 16:37:47 2026 +0200
dev-util/therock-bin: add 7.14.0_alpha20260604
commit 55cf4a6bdb1e31979ce0847932655805961280a4
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu May 28 19:35:46 2026 +0200
dev-util/therock-bin: drop 7.13.0_alpha20260508
Single-arch (gfx1150-only) build predating the 7.14 AMDGPU_TARGETS
multi-arch refactor. gfx1150 is one of the 14 targets the 7.14 nightlies
already cover, so the 7.13 ebuild served only gfx1150 and anchored no
other arch; keeping both 7.14 nightlies instead gives every target a
one-version rollback.
commit 01a9452edc8aae98a0e7e617eec7d11662d653c4
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu May 28 19:26:53 2026 +0200
dev-util/therock-bin: add 7.14.0_alpha20260528
commit 8cc549b995c912815b36e7c36284487339edc83a
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed May 20 19:28:53 2026 +0200
dev-util/therock-bin: drop 7.14.0_alpha20260516
commit 668338f5e15488ad2c9b66df95c15499b4cb0565
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed May 20 19:28:53 2026 +0200
dev-util/therock-bin: add 7.14.0_alpha20260520
commit b077dd6747dcd74388ddfeb7519a050c7da78b31
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat May 16 16:27:40 2026 +0200
dev-util/therock-bin: clarify multi-arch nature in DESCRIPTION
Tag the AMDGPU_TARGETS-driven shape explicitly so emerge -pv and metadata viewers
convey that the installed SDK is per-target.
commit b670cfce9434566765b2920690630524b26faf95
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat May 16 16:15:27 2026 +0200
dev-util/therock-bin: AMDGPU_TARGETS-driven multi-arch SDK at 7.14
Reshape the 7.14.0_alpha20260516 ebuild from gfx1150-only to a USE- flag-driven
multi-arch picker covering all 14 architectures AMD's nightly pipeline currently
produces: * 8 single-arch values matching ::gentoo's canonical
amdgpu_targets.desc: gfx900/906/908/90a (CDNA) + gfx1150/1151/ 1152/1153 (RDNA3.5
APUs). * 6 fat-bundle values declared in this overlay's new profiles/
desc/amdgpu_targets.desc: gfx101X-dgpu (RDNA1), gfx103X-all (RDNA2), gfx110X-all
(RDNA3 dGPU), gfx120X-all (RDNA4), gfx94X-dcgpu (CDNA3, MI300), gfx950-dcgpu
(CDNA4, MI350). REQUIRED_USE="^^ ( ... )" forces exactly one target — each tarball
is the full SDK rooted at WORKDIR, so /opt/therock-bin/ can only hold one variant at
a time. Switch architectures by re-emerging with a different AMDGPU_TARGETS.
Manifest populated by streaming every per-arch tarball through blake2b+sha512 without
writing to disk: 14 fresh DIST entries plus the 7.13 gfx1150 line preserved for the
older ebuild. Build-verified end-to-end via FEATURES=-xattr ebuild ... clean install
with USE=amdgpu_targets_gfx1150 — same 16 GiB staged tree as the prior single-arch
run. The companion -7.13.0_alpha20260508 ebuild stays gfx1150-only; the multi-arch
shape kicks in from 7.14 forward.
commit 3d0419f414c0cabf5af464fc2da8478d2950c3ea
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat May 16 13:00:25 2026 +0200
dev-util/therock-bin: add 7.14.0_alpha20260516
Routine nightly bump. Minor version 7.13 -> 7.14 in upstream; gfx1150 tarball
published 2026-05-16 at rocm.nightlies.amd.com/tarball/therock-dist-linux-gfx1150-
7.14.0a20260516.tar.gz (3.18 GiB, HTTP 200). Layout sanity check vs
our known-good -bin layout reference: * Flat top-level (bin/ lib/ include/ libexec/ share/
tests/ …) — unchanged, src_install cp -a remains correct. * lib/rocm_sysdeps/
vendored-libs set unchanged. * Same QA-notice scanelf findings (NULL DT_RUNPATH on
libamd_smi.so + libhsa-amd-aqlprofile64.so) — upstream-prebuilt, non-actionable
for a -bin. * Non-vendored system-lib set unchanged (toolchain + RDEPEND covers
zstd / elfutils / numactl / libcrypt / libdrm). ebuild ... install ran clean; 16 GiB
staged in image tree (same as the 7.13 build). Not re-tested at runtime against
caffe2/vllm yet.
commit 17c45d371d84ae01f8ddf69283e0166ca3008694
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat May 9 08:50:02 2026 +0200
dev-util/therock-bin: add 7.13.0_alpha20260508
Pre-built ROCm SDK from AMD's TheRock super-project, pinned to the
2026-05-08 nightly gfx1150 single-target build. Installs to
/opt/therock-bin/ and coexists with the system ROCm 7.2.3 in /usr —
no file conflicts; users opt in via per-shell ROCM_PATH/PATH/
LD_LIBRARY_PATH.
TheRock differs from our per-package ROCm 7.2.3 stack: it bundles
all ROCm subprojects (HIP, LLVM-with-AMD, math libs, profilers,
MIOpen, rocWMMA, etc.) at newer-than-tag commit SHAs, with hardware
enablement for gfx1150 (Strix Point iGPU) which the rocm.eclass 7.x
'unofficial' list exposes as a USE flag but tagged 7.2.3 sources
haven't been validated against. rccl and hipSPARSELt remain
gfx1150-excluded in TheRock 7.12 too (same upstream issues).
The distribution mostly vendors its system deps as librocm_sysdeps_*
inside its own lib/rocm_sysdeps/, so RDEPEND only covers the few
libs (libdrm, libelf, libnuma, libzstd, libcrypt) that a subset
of binaries still link against the system for. Verified end-to-end
on Strix Point: rocminfo enumerates the iGPU as Agent 2 / gfx1150
with ISA amdgcn-amd-amdhsa--gfx1150.
Distfile is a rolling-window nightly (~3 weeks of S3 retention),
so this revision is a snapshot — bump regularly or accept rot.
Mirroring to extra-stuff is impractical at 2.77 GiB.
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Aug 17 00:29:35 2026 +0200
dev-util/therock-bin: use virtual zlib provider
The binary needs the zlib ABI rather than a specific implementation. Depend on
virtual/zlib so compatible providers satisfy it without retaining the deprecated
concrete atom.
commit add5779373854b6ddbbade28bca06e5997c8ae5c
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Aug 16 17:32:30 2026 +0200
dev-util/therock-bin: add runtime deps to 7.13.0
The exact AMD payload declares Perl, Python 3, and zlib as required dependencies. Its
installed tree contains corresponding scripts and libz consumers, while its versioned
Python payload stops at 3.13.
commit 72b2759e9fda3a8dc239a14a3f738183ed530ea0
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Aug 16 16:42:35 2026 +0200
dev-util/therock-bin: drop 7.14.0-r1
AMD removed installer build 6 from the canonical release endpoint, leaving this
revision unfetchable. Build 7 supersedes it without changing the upstream ROCm
release version.
commit 6d0d25688db7535ba9f33afda83af4bd69269844
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Aug 16 16:42:03 2026 +0200
dev-util/therock-bin: add 7.14.0-r2
AMD replaced installer build 6 with build 7 at the canonical release endpoint. The
replacement payload also exposes direct Perl, Python, and zlib runtime requirements
that must not depend on incidental system packages.
commit ff6c42c265a8d760643f299305032f65db77be06
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 11:57:08 2026 +0200
dev-util/therock-bin: follow the 7.14.0 installer reissue to -6, revbump
AMD reissued the runfile and withdrew the previous one:
rocm-installer-7.14.0-5.run now 404s at repo.radeon.com while -6 serves.
The package could not be fetched at all as shipped, so this is a broken
fetch rather than a version being merely stale. PV is unchanged, which
is why MY_BUILD exists and why this is a revbump.
Re-checked the payload rather than assuming a reissue keeps its shape,
since the ebuild slices the tar out of the runfile by hand. The
structure holds: filesizes/offset arithmetic still finds the archive,
BUILDINFO still reports ROCm 7.14.0 (package version 7.14.0rc3),
component-rocm/content-base.tar.xz is present, and the same eight
content-gfx families ship -- gfx103x, gfx110x, gfx115x, gfx120x,
gfx908, gfx90a, gfx94x, gfx950 -- so AMDGPU_ARCHS still maps onto real
components.
The two revisions are close in size, 5.46 GiB each, consistent with a
reissue rather than a rebuild.
commit f998d8b358f078daf3bb7e098f2081c3a63d93bf
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 11:54:43 2026 +0200
dev-python/vllm: drop the orphaned f5bc33c flash-attn patch
Each flash-attn patch is named for the commit the ebuild pins, since
the filename is built from $. f5bc33c was pinned by
0.21.0, which is no longer in the tree, and nothing else references it
-- the only occurrence of the hash anywhere is inside the patch's own
diff header.
The four live pins each still have their patches: bce2942 for 0.22.1,
dd62dac for 0.23.0 and 0.24.0, 2c839c3 for 0.25.x and caaa4eb for
0.26.0.
commit d3638af0135e0fc98e4e03162e9778de73a73323
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jul 16 14:39:33 2026 +0200
dev-util/therock-bin: add 7.13.0
Packaged from rocm-installer-7.13.0-3.run the same way as 7.14.0, and kept
alongside it. sci-ml/lemonade pins ROCm 7.13.0 for its rocm-stable backend
and reuses a system ROCm only on a major.minor match, so a 7.13.0 tree
(/opt/therock-bin/.info/version = 7.13.0) is what lemonade's USE=system-therock
points lemond at; 7.14.0 stays for general newest-ROCm use.
7.13's runfile differs structurally from 7.14's: the gfx115x arches ship as
separate per-arch content tarballs (content-gfx1150/1151/1152, no gfx1153), so
_therock_family maps each to its own tarball while the rest stay coarse
families. Internally 7.13.0rc2 (VERSION), no BUILDINFO.
commit 0d0489459653c936c2e23220f8e3b11e2b6285d0
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jul 16 13:05:55 2026 +0200
dev-util/therock-bin: repackage from the 7.14.0 release runfile
AMD ships the ROCm 7.14.0 release only as a Makeself runfile installer
(rocm-installer-7.14.0-5.run) -- there is no per-arch release tarball. The
therock-dist-linux-*.tar.gz form exists as nightly a<DATE> snapshots only,
the therock-X.Y GitHub releases carry no assets, and the source tag is just
TheRock's build system. Drop the two nightly snapshot ebuilds and package the
release itself:
- SRC_URI is the .run (Makeself 2.4.2, COMPRESS=none). src_unpack slices the
uncompressed tar payload out by offset (file size minus the header's
filesizes var; stat -L since portage symlinks the distfile) without running
the installer, then extracts component-rocm/content-base.tar.xz plus the
selected arch's content-gfx<family>.tar.xz.
- src_install flatten-merges each component's rocm/core-7.14 subtree into
/opt/therock-bin. The libraries are $ORIGIN-rpath relocatable, so no
patchelf, keeping the ROCM_PATH=/opt/therock-bin runtime model.
- IUSE moves to the release's fine-grained amdgpu_targets (the gfx110x/115x/
120x members plus gfx1030/gfx908/gfx90a/gfx942/gfx950); the release drops
the gfx900/gfx906/gfx101x that the nightly carried.
The .run is internally 7.14.0rc3 build -5 but is the official 7.14.0 release;
MY_BUILD tracks the installer revision for a rebuild.
commit e449031d82a8aeb615ee2c8f3b546446e708ccb0
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Jun 20 12:07:50 2026 +0200
dev-util/therock-bin: drop 7.14.0_alpha20260604
commit a9cb82bf6fd696bac63033b1605ac200087524b7
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Jun 20 12:07:50 2026 +0200
dev-util/therock-bin: add 7.14.0_alpha20260612
commit b808b79b04aa887e34b891b3c8b70cc27e8dcb41
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jun 11 14:56:51 2026 +0200
dev-util/therock-bin: drop 7.14.0_alpha20260528
commit b347871109e95b6d223c9ce0994896f41dad5b43
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jun 11 14:56:07 2026 +0200
dev-util/therock-bin: add 7.14.0_alpha20260611
commit df145c795a85b4d34d2b92359b984483b7c039ee
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jun 4 16:38:01 2026 +0200
dev-util/therock-bin: drop 7.14.0_alpha20260520
commit 3f2af3009223025fb8cea3c54d37915c7949ed1e
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jun 4 16:37:47 2026 +0200
dev-util/therock-bin: add 7.14.0_alpha20260604
commit 55cf4a6bdb1e31979ce0847932655805961280a4
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu May 28 19:35:46 2026 +0200
dev-util/therock-bin: drop 7.13.0_alpha20260508
Single-arch (gfx1150-only) build predating the 7.14 AMDGPU_TARGETS
multi-arch refactor. gfx1150 is one of the 14 targets the 7.14 nightlies
already cover, so the 7.13 ebuild served only gfx1150 and anchored no
other arch; keeping both 7.14 nightlies instead gives every target a
one-version rollback.
commit 01a9452edc8aae98a0e7e617eec7d11662d653c4
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu May 28 19:26:53 2026 +0200
dev-util/therock-bin: add 7.14.0_alpha20260528
commit 8cc549b995c912815b36e7c36284487339edc83a
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed May 20 19:28:53 2026 +0200
dev-util/therock-bin: drop 7.14.0_alpha20260516
commit 668338f5e15488ad2c9b66df95c15499b4cb0565
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed May 20 19:28:53 2026 +0200
dev-util/therock-bin: add 7.14.0_alpha20260520
commit b077dd6747dcd74388ddfeb7519a050c7da78b31
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat May 16 16:27:40 2026 +0200
dev-util/therock-bin: clarify multi-arch nature in DESCRIPTION
Tag the AMDGPU_TARGETS-driven shape explicitly so emerge -pv and metadata viewers
convey that the installed SDK is per-target.
commit b670cfce9434566765b2920690630524b26faf95
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat May 16 16:15:27 2026 +0200
dev-util/therock-bin: AMDGPU_TARGETS-driven multi-arch SDK at 7.14
Reshape the 7.14.0_alpha20260516 ebuild from gfx1150-only to a USE- flag-driven
multi-arch picker covering all 14 architectures AMD's nightly pipeline currently
produces: * 8 single-arch values matching ::gentoo's canonical
amdgpu_targets.desc: gfx900/906/908/90a (CDNA) + gfx1150/1151/ 1152/1153 (RDNA3.5
APUs). * 6 fat-bundle values declared in this overlay's new profiles/
desc/amdgpu_targets.desc: gfx101X-dgpu (RDNA1), gfx103X-all (RDNA2), gfx110X-all
(RDNA3 dGPU), gfx120X-all (RDNA4), gfx94X-dcgpu (CDNA3, MI300), gfx950-dcgpu
(CDNA4, MI350). REQUIRED_USE="^^ ( ... )" forces exactly one target — each tarball
is the full SDK rooted at WORKDIR, so /opt/therock-bin/ can only hold one variant at
a time. Switch architectures by re-emerging with a different AMDGPU_TARGETS.
Manifest populated by streaming every per-arch tarball through blake2b+sha512 without
writing to disk: 14 fresh DIST entries plus the 7.13 gfx1150 line preserved for the
older ebuild. Build-verified end-to-end via FEATURES=-xattr ebuild ... clean install
with USE=amdgpu_targets_gfx1150 — same 16 GiB staged tree as the prior single-arch
run. The companion -7.13.0_alpha20260508 ebuild stays gfx1150-only; the multi-arch
shape kicks in from 7.14 forward.
commit 3d0419f414c0cabf5af464fc2da8478d2950c3ea
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat May 16 13:00:25 2026 +0200
dev-util/therock-bin: add 7.14.0_alpha20260516
Routine nightly bump. Minor version 7.13 -> 7.14 in upstream; gfx1150 tarball
published 2026-05-16 at rocm.nightlies.amd.com/tarball/therock-dist-linux-gfx1150-
7.14.0a20260516.tar.gz (3.18 GiB, HTTP 200). Layout sanity check vs
our known-good -bin layout reference: * Flat top-level (bin/ lib/ include/ libexec/ share/
tests/ …) — unchanged, src_install cp -a remains correct. * lib/rocm_sysdeps/
vendored-libs set unchanged. * Same QA-notice scanelf findings (NULL DT_RUNPATH on
libamd_smi.so + libhsa-amd-aqlprofile64.so) — upstream-prebuilt, non-actionable
for a -bin. * Non-vendored system-lib set unchanged (toolchain + RDEPEND covers
zstd / elfutils / numactl / libcrypt / libdrm). ebuild ... install ran clean; 16 GiB
staged in image tree (same as the 7.13 build). Not re-tested at runtime against
caffe2/vllm yet.
commit 17c45d371d84ae01f8ddf69283e0166ca3008694
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat May 9 08:50:02 2026 +0200
dev-util/therock-bin: add 7.13.0_alpha20260508
Pre-built ROCm SDK from AMD's TheRock super-project, pinned to the
2026-05-08 nightly gfx1150 single-target build. Installs to
/opt/therock-bin/ and coexists with the system ROCm 7.2.3 in /usr —
no file conflicts; users opt in via per-shell ROCM_PATH/PATH/
LD_LIBRARY_PATH.
TheRock differs from our per-package ROCm 7.2.3 stack: it bundles
all ROCm subprojects (HIP, LLVM-with-AMD, math libs, profilers,
MIOpen, rocWMMA, etc.) at newer-than-tag commit SHAs, with hardware
enablement for gfx1150 (Strix Point iGPU) which the rocm.eclass 7.x
'unofficial' list exposes as a USE flag but tagged 7.2.3 sources
haven't been validated against. rccl and hipSPARSELt remain
gfx1150-excluded in TheRock 7.12 too (same upstream issues).
The distribution mostly vendors its system deps as librocm_sysdeps_*
inside its own lib/rocm_sysdeps/, so RDEPEND only covers the few
libs (libdrm, libelf, libnuma, libzstd, libcrypt) that a subset
of binaries still link against the system for. Verified end-to-end
on Strix Point: rocminfo enumerates the iGPU as Agent 2 / gfx1150
with ISA amdgcn-amd-amdhsa--gfx1150.
Distfile is a rolling-window nightly (~3 weeks of S3 retention),
so this revision is a snapshot — bump regularly or accept rot.
Mirroring to extra-stuff is impractical at 2.77 GiB.