Skip to content
Snippets Groups Projects
Simon McVittie's avatar
Simon McVittie authored
This made them usable from outside the LD_LIBRARY_PATH runtime, but breaks
their use inside a pressure-vessel container. In pressure-vessel, the
glibc family of libraries are typically taken from outside the container
(for example /overrides/lib/x86_64-linux-gnu/libc.so.6), and the dynamic
linker ld.so is replaced with one that is suitable for the libraries
in /overrides. In general, these versions will be incompatible with the
ones in /usr/lib/x86_64-linux-gnu, which unfortunately are the ones that
get pulled in via the DT_RPATH.

This reverts commit 91478a07.

Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
a32d9290
History

steam-runtime-tools — Steam Runtime integration for the Steam client

The steam-runtime-tools library provides low-level Unix-specific tools and functionality for the Steam client.

To support multiple architectures (currently only i386 and x86_64 are supported), you will need to build it once for each architecture and install at least the helper tools in /usr/libexec/steam-runtime-tools-0 (the libsteam-runtime-tools-0-helpers package) for every architecture in parallel.

The helper tools are located relative to the shared library, so it's OK to bundle steam-runtime-tools alongside some other stack in this layout:

anything/
    lib/
        x86_64-linux-gnu/
            libsteam-runtime-tools-0.so.0
    libexec/
        steam-runtime-tools-0/
            i386-linux-gnu-*
            x86_64-linux-gnu-*

as long as the program that is linked to libsteam-runtime-tools-0.so.0 can find it (via a RPATH or RUNPATH or by setting the LD_LIBRARY_PATH environment variable).