summaryrefslogtreecommitdiff
path: root/guides
diff options
context:
space:
mode:
authorKévin Le Gouguec <kevin.legouguec@gmail.com>2025-02-06 08:10:30 +0100
committerKévin Le Gouguec <kevin.legouguec@gmail.com>2025-02-06 08:10:30 +0100
commit758b451fcc3e4c25bc33567df3057e7a9a06586a (patch)
tree636118eb0c22a3b93059d2c10f70669184993406 /guides
parenta81b07cc09bd27e79c775bf8b8f0897cbbbc1e44 (diff)
downloadmemory-leaks-758b451fcc3e4c25bc33567df3057e7a9a06586a.tar.xz
Add some clarifications re. building Mesa
Mostly as a pretext to stick a footnote. There shall be margin notes in this saga, so says I.
Diffstat (limited to 'guides')
-rw-r--r--guides/sysadmin/machines/amdahl30/killing-time.org14
1 files changed, 11 insertions, 3 deletions
diff --git a/guides/sysadmin/machines/amdahl30/killing-time.org b/guides/sysadmin/machines/amdahl30/killing-time.org
index 835c26a..0b70791 100644
--- a/guides/sysadmin/machines/amdahl30/killing-time.org
+++ b/guides/sysadmin/machines/amdahl30/killing-time.org
@@ -241,9 +241,17 @@ not overwork it to death?
- {{{narrator(10 false leads later)}}}
- The factory@ announcements say Mesa was upgraded from 24.2.7 to
24.3.0 in snapshot 20241124. The Mesa docs explain how to test
- "local" (uninstalled) builds (kudos!) so gave it a shot: a
- freshly built 24.2.7 behaves exactly like the current version,
- so no smoking gun there.
+ "local builds" (i.e. uninstalled; kudos![fn:mesa-builddeps]) so
+ gave it a shot: a freshly built 24.2.7 behaves exactly like the
+ current distro version (24.3.4), so no smoking gun there.
+
+[fn:mesa-builddeps] Took some trial-and-error to get a build going:
+~zypper source-install --build-deps-only Mesa~ did not cut it.
+Probably should have looked at Tumbleweed's spec file to get a
+matching build configuration; instead ~zypper install~'ed my way to
+victory - needed ~libclc llvm llvm-devel libLLVMSPIRVLib-devel clang
+clang-devel python3-ply rust rust-bindgen rust-cbindgen~.
+
- In [[https://gitlab.freedesktop.org/upower/power-profiles-daemon/-/issues/164][upower/power-profiles-daemon#164]], @Nyan reports problematic iGPU
capping; not convinced this is applicable though, given the reported