fix: x86-64 Steam client fails without the KDE desktop (FEX r5 bundles libxxhash) (#1050)

FEX r4 links libxxhash, which the Linux runtime does not ship; devices
without the KDE desktop package (where the library came from) exited 127
at the x86-64 client's first FEX call. FEX r5 bundles it beside libFEXCore
with RUNPATH $ORIGIN/../lib, and the FEX build now fails when a program in
the package needs a library that is neither bundled nor listed in
tools/fex/runtime-libs.txt. droiddeck-steam-x64 moves to fex-2610-r5
(DroidDeck-Components #5). Progress log: the org review of #152 and this fix.
This commit is contained in:
The412Banner authored and GitHub committed 2026-10-18 02:00:29 -04:00
1 parent db8d1c9910
commit 798386d02a
5 files changed
+61 -6

No files matched your search

+4 -2
View File
@@ -193,8 +193,10 @@ alone would then read as an installed client.
reproducible, so a tag is never rebuilt over. The release is never the repo's Latest nor a
pre-release: it is a component fetched by tag, not something users install.
- Releases so far: `fex-2609-r2` (no thunks), `fex-2609-r3` (thunks), `fex-2610-r1`, `fex-2610-r2`,
`fex-2610-r3`, `fex-2610-r4` (current: in-root resolution when openat2 is missing, exact MAP_32BIT
marking). They were built and published in The412Banner/DroidDeck; up to r3 their tags point at that
`fex-2610-r3`, `fex-2610-r4` (in-root resolution when openat2 is missing, exact MAP_32BIT
marking), `fex-2610-r5` (current: bundles libxxhash, which the Linux runtime does not ship; the
build fails when a program in the package needs a library that is neither bundled nor listed in
`tools/fex/runtime-libs.txt`). They were built and published in The412Banner/DroidDeck; up to r3 their tags point at that
repository's `main`, from r4 at the commit each was built from.
- **Where the app gets it.** The app downloads FEX from Droid-Deck/DroidDeck-Components, where nothing is
uploaded by hand: a new tag is published by `build-fex.yml`, recorded in that repository's `fex.json`